Re: [MiNT] Keyboard-problem with XaAES helmut-branch

[Jo Even Skarstein <joska@online.no>]

On 06/11/2010 11:09 PM, Helmut Karlowski wrote:

> That's the problem with this issue. I've been having this since MiNT
> 1.15. Maybe Ctrl-S helps to reproduce it.

I have not noticed this until tonight.

>>> How is clipbrd set in you xaaes.cnf? I get this message when I set
>>> clipbrd=\host\clipbrd\ on aranym but not when it's c:\clipbrd\
>>
>> clipboard = u:\ram\clipbrd
> 
> What does it say with c:\clipbrd? Does toswin copy/paste work? IMHO qed
> is buggy what clipbrd concerns.

toswin copy/paste works fine. qed copy/paste also works, but only
internal to qed since it doesn't use the clipboard.

Setting clipbrd to point to c:\clipbrd works. When set to
u:\ram\clipbrd, qed complains when this folder already exists. However,
this problem has never occured until tonight. So something has changed.

>>> How do you start xaaes?
>>
>> from init ("console "/c/mint/1-17-cur/xaaes/xaloader.prg" in ttytab).
> 
> That would explain the keyboard-issue. I only have this when XaAES is
> started from a shell, never from mint.cnf.

I have not noticed this problem before tonight. I have been using this
setup (EasyMiNT) since 2007.

>> Btw I just noticed another issue. Taskbar stops receiving events after a
>> while with this build. Has anybody else noticed this? I will look into
>> it ASAP.
> 
> Strange.

Indeed. Something is seriously wrong with Taskbar when run under the
latest build of XaAES. Common tasks that works fine with previous
XaAES-builds cause crashes with the latest build. No memory violations
or anything, just a solid lock-up of the AES. Switch back to the build
from September, and everything is fine. I'll look closer into this.

Jo Even