Togglesnap in DK .91

[Terry]

Just upgrade to DK .91 and I can't get the Togglesnap to work.

ToggleSnap= 1
ToggleTime= 4000

The snap shows up just fine, but it will not toggle to the title screen.   When I navigate to a game in the game list and let it sit (waiting for the snap/title to toggle), after exactly 60 seconds, DK gets a "run-time error '53':  File not found", and then it crashes.

Everything works just fine in DK .81.  My dir.ini file looks like this (same one I used in .81):

[Dirs]
***Enter all your rom paths... Just like you do in a mame.ini

roms=c:\mame\files\roms;c:\mame\daphne\framefile\


***Put These in as a base folder.  I.E. If your snaps are in "e:\mame\snap\"
***then the entry should be: "e:\mame\"

Primary Artwork Dir=c:\mame\files\
Additional AW Dirs=c:\mame\files\daphne\

***The alternate elements allow you to have two more artwork elements besides the usual.
***Simply put the name of the sub folder (like "\controls\").
***Note:  Skins must have an alt-element slot defined for this to work.  

AltElement1=
AltElement2=

And my game lists are working just fine.

I created my skin in skinner 3.0.  I also tried openning it in skinner 5.0 and then re-saving it, but it still doesn't work.  Is there something different between .81 and .91 as far as the togglesnap that I need to set up?

Everything else works great so far in .91.

Thanks.

[Terry]

Ok, I figured out the 60 second run time error was because I had the screensaver option set to 60 seconds in DK, and there was no path or name defined in my frontend.ini file.  I turned this option off, no more run time error.  But still no toggles.

I was also messing around with emusaver2.1.  But I observed something that both DK .81 and .91 have in common.  When DK is running, it seems to override the windows screensaver options.  For example.  No matter what screensaver and wait time I have selected in my display properties, DK will just sit there and never run windows screen saver.  This is fine since DK has it's own screensaver settings built in.

But how is emusaver2.1 suppose to work?  It is based on the windows screensaver options, and if DK will not respond to them, emusaver will never run.  This is the problem I have run into.

Is there a setting I am overlooking?  All files are in place and seem to be working per the emusaver readme file.

Thanks.

[Terry]

Emusaver works just fine now.  I realized that I need to launch emusaver.scr from within the DK screensaver options.    The windows screen saver properties are just used to set it up, not to run it (at least within DK).

So now back to my original Togglesnap problem.

[Howard_Casto]

Thank you for bringing this to my attention.....  It appears I accidentally removed a variable when I moved around the main function.  The toggletime never got passed to the timer and thus the snap never changed.  I will have a new release shortly which fixes this and a few other bugs I've found.  


Btw the disabling of the default windows screensaver is intentional.  I do this because if you put a game on pause within mame or other emulators, the windows screensaver can kick in and corrupt the screen, making it impossible to continue your game.  (if it's coded badly, which many are)
 
By disabling this I get manual control of the screensaver and thus I can have it only enable when you are within dk.  You can still use any screensaver you like, you simply point the screensaver path to the windows directory and the ss name to the name of the scr file.  As dk simulates the windows screensaver call, it should work just fine.  

[Terry]

Sounds good.  I will be looking forward to your next release.

Thanks for the explanation of the screen saver.  It's making sense to me now.

Terry