Menu

#1016 pressing the "save" button in "settings" simply closes Vice

v3.2
closed-fixed
nobody
None
GTK3
2018-06-02
2018-05-31
Querino
No

pressing the "save" button in "settings" simply closes Vice.

  • Win 7
  • GTK3VICE-3.2-win32

Discussion

  • Querino

    Querino - 2018-05-31

    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.

     
  • compyx

    compyx - 2018-06-01

    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?

     
  • compyx

    compyx - 2018-06-01

    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.

     
  • Greg King

    Greg King - 2018-06-01

    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
  • Greg King

    Greg King - 2018-06-01

    When debugging VICE from within MSYS2 or Cygwin, you should copy the executables from src/ into data/; then, run them from there. You won't need a special configuration. You even can add a line in your ~/.bash_profile that appends the full path, to that directory, to the PATH variable. 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
  • compyx

    compyx - 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'?

     
  • Greg King

    Greg King - 2018-06-01

    I use this "pipeline command" in bash:

    time make&&cp -vu src/*.exe data
    

    I simply "recall" bash's command history whenever I want to rebuild VICE; I don't need to remember or type much.

     
  • compyx

    compyx - 2018-06-01

    Yep. After I typed my comment, I thought about just adding && cp bins-to-data to make and indead using bash'es history (up). I'd have alter it a bit though, I build out-of-tree, so it would become something like make && cp src/*.exe ../vice/data, and then run ../vice/data/x64.exe.

     
  • Greg King

    Greg King - 2018-06-02

    Yep, this one was "closed-fixed" before it was openned.

     
  • compyx

    compyx - 2018-06-02
    • status: open --> closed-fixed
     
  • compyx

    compyx - 2018-06-02

    :-)

    Closing.

     

Log in to post a comment.

MongoDB Logo MongoDB