Hatari (Atari ST Support)

A nice (keyboard based) front end for Arcade / Console game emulators.

Moderator: battlecat

Hatari (Atari ST Support)

Postby Zombie » Tue Feb 22, 2011 7:42 am

I'm entertaining configurations for Atari ST Support.
User avatar
Zombie
 
Posts: 791
Joined: Mon Oct 06, 2008 2:52 pm

Re: Hatari (Atari ST Support)

Postby Zombie » Sat Mar 05, 2011 3:47 pm

You can easily configure this in the ~/.hatari/hatari.cfg file: Set bConfirmQuit = FALSE and set the keyQuit settings to the key of your choice.

These don't need to be set in the system default configuration, one can have a separate configuration file that contains only the options that you want to override from the default config. You can specify your own config with --configfile option.

If you want to send Hatari commands or change its configuration while it's running, you can send them using Hatari's command socket, specified with the --control-socket option. Try hconsole.py to see how that works.

The latest (not yet released) version of Hatari has also support (hack) for running programs directly with Hatari just with "hatari dir/some.prg".
Almost any program that doesn't need to be run from the auto/ -folder seems to be working fine with it.

Related to this, there's also tools/hatari-tos-register.sh init script you can use to register Hatari as a handler for Atari programs. After running that you can start Atari programs directly from your Linux desktop. This of course assumes that Hatari's configured for the Atari type (ST/STE/TT/Falcon) that the Atari program that you clicked expects, but if you know what you do, you can get around that too.

Finally, if you want to embed Hatari window inside Arcade launcher UI, see the hatariui.py for PyGtk code on how to do it using Gtk Plug/Socket widget and hatari.py for what environment variable you need to set for Hatari to embed itself into your program.

Note: The embedding is done in a slightly unorthodoxly as embedding support
is slightly broken in both SDL and Gtk. SDL's own embedding support
disables keyboard input (as can be verified from SDL sources), so embedding
support is built directly into Hatari itself. And Gtk steals keys from the
embedded window unless you disable that in the surrounding Gtk widgets
(= you cannot have keyboard shortcuts in your own program if you want keys
to work in the embedded program). That happens at least for embedded
programs that don't implement full XEmbed protocol...
User avatar
Zombie
 
Posts: 791
Joined: Mon Oct 06, 2008 2:52 pm

Re: Hatari (Atari ST Support)

Postby codebase » Mon Mar 14, 2011 6:52 am

Hi,

I'm new here.
Hatari's current version (as of this writing version 1.4.0) seems to have the support you talk about. For wahcade to work all you need to do is make a config file for each system. Then use the following config for wahcade.
This is just an example of the config I used for the Atari Falcon but it can be easily modified for any system supported by Hatari. Note: you need to give your own path to the config files.
Atari Falcon
Code: Select all
### Hitari Atari Falcon (wahcade v0.23) ###

emulator_title                          Atari Falcon

### List Generation Settings ###
rom_path                                ~/emulators/atari2600/roms
rom_extension                         a26
dat_file                               
nms_file                               
catver_ini_file                         
list_generation_method                  rom_folder

### Execution Settings ###
emulator_executable                     /usr/bin/hatari
commandline_format                     --fullscreen --confirm-quit false --config-file "~/.hatari/Atari Falcon.cfg" "[rompath]/[name].[romext]"
alt_commandline_format_1               
alt_commandline_format_2               
game_specific_config_path               

### Artwork Locations ###
artwork_1_image_path                    ~/emulators/atari2600/snapshots
artwork_2_image_path                   
artwork_3_image_path                   
artwork_4_image_path                   
artwork_5_image_path                   
artwork_6_image_path                   
artwork_7_image_path                   
artwork_8_image_path                   
artwork_9_image_path                   
artwork_10_image_path                   
movie_preview_path                     
movie_artwork_no                        1

### Screen-Saver Settings ###
enable_music_in_screensaver             0
saver_type                              slideshow
movie_path                             
movie_fullscreen                        1
quit_delay                              30
wrapper_executable                     
wrapper_commandline_format              [name]
scr_file                               

### External Application Settings ###
ipc_file_or_path                       
app_1_executable                       
app_1_commandline_format               
app_2_executable                       
app_2_commandline_format               
app_3_executable                       
app_3_commandline_format               
auto_launch_apps                       

### Additional Settings ###
music_path                             
lcd_display_file_path                   
lcd_fe_text                             

### Settings used by MAMEWAH ###
current_list                            0

### Added in v0.99pre8 "Could it be?" ###
list_title                             
cycle_list                              0



Just make one for each system you wish to support, with the appropriate config file chosen. That's all there is to it.
codebase
 
Posts: 1
Joined: Mon Mar 14, 2011 6:34 am


Return to Wah!Cade

Who is online

Users browsing this forum: Bing [Bot] and 2 guests

cron