Re: [openMSX-devel] Proposal for config files! Separation of emu-config and MSX-config...

[Patriek L. <pat...@dd...>]

Maarten ter Huurne wrote:
>On Friday 27 December 2002 22:29, Patriek Lesparre wrote:
> > No need for conversion as Windows handles the '/' seperator just fine ever
> > since Win95.
>
>The syscalls can handle '/', but can the GUI classes (file open dialog etc)?

I just checked (with 2 different programs) on Win98SE and indeed, the 
standard File Open Dialog do not accept '/'. :( At least the command line 
interface does support them.

However, I think it's clear MicroSoft is slowly moving away from the 
backslash, and I wouldn't be surprised if Windows XP supported it even more 
(especially with POSIX-based NT-core and the internet integration all over 
the place).
Though that doesn't help openMSX much ^^;

Is openMSX planning to use the Win32 GUI classes as user interface?

>In any case, the users are accustomed to '\', so every time we show a path to
>the user it should be in '\' notation.
>
>Also, it is important to refuse '\' in config files.

How do these 2 remarks mix? Users are accustomed to the backslash, but they 
have to use 'strange' forward slashes in config files?

If you're going to enforce using '/', you'd better consistently display '/' 
as well. Otherwise I think it will just lead to confusion and emails with: 
"My config files generate an error in openMSX, please help!"

Now that I think of it, those kind of emails can be expected in any case 
^^; You can only solve it by supporting both \ and / (also on linux), 
because even an "You are using \ in your config file paths, please read the 
manual" will not stop the clueless from emailing.

However, if I were you I'd enforce '/' and display '/' always. openMSX will 
probably attract the more intelligent of users anyway (those who wanna play 
'r0Mz' use 'warez0red' fMSX-Win just because it costs money :P), and I'm 
pretty sure the Japanese are fed up using Yen-signs as directory seperators 
anyway :)

*sigh* The things you have to deal with in a multiplatform application :P

Greetz,
         Patriek