Re: [hatari-devel] Hatari windows builds

[ Thread Index | Date Index | More Archives ]

Ok so I downloaded the SDL1 build - changing nothing else - and fired it up. F10 immediately opens the debugger as it should.

Seems conclusive :)

Thanks again,

On 3 March 2015 at 13:03, Douglas Little <doug694@xxxxxxxxxxxxxx> wrote:
Hi Laurent,

Well, neither of my PC keyboards has a 'FN' key. On my Mac - sure, but not my PC. :)

Regardless, I've always been able to access the debugger in earlier Windows builds, without such a key. And I was easily able to map the keys via the config file (e.g. to F10). So something must have changed.

SDL2 sounds like it might be involved so I will do some more experiments and report later.


On 3 March 2015 at 12:58, <laurent.sallafranque@xxxxxxx> wrote:
Hi Doug,

I've tested on a windows computer here (give me my linux ;)

So, my command line is :

start ./hatari_debug.exe -W

Yes, it's -W, not -D

To pause hatari, I use : "ALT-GR" + PAUSE

To enter the debugger, I use : "ALT-GR" + "FN" + PAUSE

"FN" is a function key just on the left of the "Windows key" on my keyboard.

At first, when you launch hatari-debug, have you got a "console window" that opens in background ?
If yes, this should be OK.



----- Mail original -----
De: "Douglas Little" <doug694@xxxxxxxxxxxxxx>
À: hatari-devel@xxxxxxxxxxxxxxxxxxx
Envoyé: Mardi 3 Mars 2015 13:54:02
Objet: Re: [hatari-devel] Hatari windows builds

Aha, good point. I was using the SDL2 version, which is a change from previous builds.... Will try SDL1...


On 3 March 2015 at 12:40, Thorsten Otto < halgara@xxxxxxxx > wrote:

> some of the mapped keys were appearing as very large integers:

Might have to do with the SDL version being used. SDL2 uses completely different internal numbers than SDL 1.2.x.

Douglas Little < doug694@xxxxxxxxxxxxxx > schrieb am 13:08 Dienstag, 3.März 2015:

BTW it may be completely unrelated, but I had issues with key mappings in the past - and found that I when I saved a new config file, some of the mapped keys were appearing as very large integers:


keyOptions = 1073742048

I think it may have been the OSX build, probably around 1.7-1.8. I put it down to a bug in that release and just c&p'd these large keycodes around in the config until I got access to the functions I needed. Using the 'normal' keycodes in that build resulted in unresponsive keys.

There's a narrow possibility it was an earlier Windows build though - I have a Win VM on my mac for portable Atari dev..... (yes too many machines & platforms - ugh)


On 3 March 2015 at 12:00, Douglas Little < doug694@xxxxxxxxxxxxxx > wrote:

Doing so just pauses emulation. Any control key plus pause/break just pauses or does nothing.

Regardless - for some reason it ignores changes to other key assignments in my config file so that alone is probably not good news :)


On 3 March 2015 at 11:55, Christer Solskogen < christer.solskogen@xxxxxxxxx > wrote:

On Tue, Mar 3, 2015 at 12:47 PM, Douglas Little < doug694@xxxxxxxxxxxxxx > wrote:
> [Sorry, forgot to reply-all!]
> Hi,
> This is what I get for F10 (Debugger) - which does nothing

I'm pretty sure you should press alt+pause/break to get to the debugger..


Mail converted by MHonArc 2.6.19+