pressing the "save" button in "settings" simply closes Vice
Versatile Commodore Emulator
Brought to you by:
blackystardust,
gpz
wrong title, sorry. :( text recovery addon filled in the wrong form.
is there a public TODO list? the monitor is not available, i guess this is on the list too.
http://vice-emu.pokefinder.org/index.php/Todo#GTK3_UI
Could you check if the vice config dir is available and writable? On my Win7 VM it's
C:\Users\$USER\AppData\Local\vice, but I've seen instances where 'Roaming' is used instead of 'Local'.If that dir is there, is there a vice.ini? And if vice.log is there, what does it say?
Strange, the experimental Gtk3-Windows build we released immediately quits when running clicking Save, but the SVN based Gtk3-Windows I just built and made a bindist of, saves the settings just fine.
The only difference config-wise is the addition of --enable-debug-gtk3ui, but all that does is make the debug_gtk3() function print data on stdout.
Note (also to self): when running x64 from the MSYS2 prompt with -directory ../alldata to have C64 & DRIVES files available and then saving settings, there will be a directory=../alldata line in vice.ini. That needs to be removed when running the bindist version, otherwise the emu won't find the data files it needs. Or use x64.exe -default.
Anyway, I've added some extra debugging to archdep.c, so perhaps you could build Gtk3 again (with --enable-debug-gtk3ui) and see what it does? If it still fails, please post the console output (esp. the "[debug-gtk3] ..." lines and the vice.log.
The Windows version of
archdep_make_backup_filename()wasn't implemented when v3.2.0 was released; it exits VICE.Last edit: Greg King 2018-06-01
When debugging VICE from within MSYS2 or Cygwin, you should copy the executables from
src/intodata/; then, run them from there. You won't need a special configuration. You even can add a line in your~/.bash_profilethat appends the full path, to that directory, to thePATHvariable. Then, commands such as"x64sc disk.d64"will work as they do on Linux.(But, VICE's manual cannot be found while using that set-up.)
Last edit: Greg King 2018-06-01
Thanks Greg, completely missed that commit by McMartin adding the backup-filename function, That indeed explains why it now "magically" works.
The copy-bins-to-data/ is also a nice 'trick', though then I'd have to remember to copy the bins each time after a
make, But it will help with running the binaries using clicking on them via Windows Explorer.So I suppose we can now close this as 'closed-fixed'?
I use this "pipeline command" in bash:
I simply "recall" bash's command history whenever I want to rebuild VICE; I don't need to remember or type much.
Yep. After I typed my comment, I thought about just adding
&& cp bins-to-datatomakeand indead using bash'es history (up). I'd have alter it a bit though, I build out-of-tree, so it would become something likemake && cp src/*.exe ../vice/data, and then run../vice/data/x64.exe.Yep, this one was "closed-fixed" before it was openned.
:-)
Closing.