Hacktarux said:
yep, it's released and i'm waiting your bug reports in this thread
A few gui_gtk glitches I noticed:
- The rombrowser column width settings are stored only if the main gui_gtk window is closed (in callback_mainWindowDeleteEvent(...)). The File -> Exit menu item directly calls gtk_main_quit(), without a callback that stores gui_gtk.conf. In configdialog.c, the file gui_gtk.conf is written, but without first updating the g_Config structure using the GTK allocation widths, resulting in gui_gtk.conf to be written with all column widths set to '0' (and if you then exit mupen64 with File->Exit or due to a crash, upon startup these 0-width values are read and set).
Suggested fix:
1. Add callback_fileExitEvent(..), similar to callback_mainWindowDeleteEvent(..)
2. Refactor the g_Config update code out of mainWindowDeleteEvent(..) into a seperate function and call this from configdialog.c as well, before config_write()
3. Allow graceful handling of old (broken) gui_gtk.conf files, by changing gui_gtk/config.c, to use something like:
(line 120)
int readValue=0;
sscanf( p, "%d", &readValue );
if (readValue>0) g_Config.iRomBrowserColWidth
=readValue;
- The stored rom browser column widths grow by 1 pixel each time.
This is probably due to GTK+-1.2 not providing a reliable, theme-independent way to obtain current CList column widths. A quickfix is changing to g_Config.iRomBrowserColWidth = w-1, but I'm afraid that won't work with all themes.