Re: [openMSX-devel] screenshot feature

[Manuel B. <ma...@ms...>]

Maarten ter Huurne wrote:
> It's not really customary for interactive programs to write to the current 
> working directory, I think. But where should screenshots be written to?
> 
> Some options:
> - home directory
> - ~/.openMSX
> - new fixed directory in home dir
> - configurable using a setting (but what is the default then?)
> 
> And what is the Windows equivalent?

Same as with the persistent data, I think.
So in Linux: put the screenshots in: ~/.openMSX/screenshots
in Windows: My Documents/openMSX/screenshots (or whatever the dir is 
that contains the persistent dir).

> I think we should bind screenshot to a key by default. Then the user can 
> choose whether to make a shot with the console or without, by enabling or 
> disabling the console. It can be useful to have to console in the shots, for 
> example if someone is reviewing openMSX and wants to explain the console, or 
> if you're debugging something and want to document the last things you did.

Agreed.

>>Some other idea:
>>- maybe we should change the default bind of full screen from PrtScr to
>>something else. PrtScr could be used for screenshots instead, like it
>>would do normally on a Windows machine anyway.
> 
> 
> That would make sense.
> 
> What key do we bind full screen to then? Most programs have it bound to "F" 
> but that's not an option for openMSX.

WOuld it be possible to use a modifier? Alt-Enter seems quite default 
then, at least in Windows. I don't mind using this for openMSX too.

> Now that we're talking about key bindings: I often accidentally press F12 when 
> I want to press another key, especially PrtScr. I read in one of the msx.org 
> threads that I'm not the only one with that problem. So maybe we can bind 
> "quit" to another key? Or maybe to a key combination? Or maybe not bind it at 
> all and have people use either the "close window" button or "quit" on the 
> console.

I like having a quit button, but that's personal. :) Of course users can 
change it themselves.

In some version of Catapult we should implement a 'save current options 
as defaults' feature, writing the settings.xml file. Keybindings could 
be edited that way too.

-- 
Grtjs, Manuel

PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ )
PPS: Visit my homepage at http://manuel.msxnet.org/