Next topic

[polygone]

Yay options panel

[Josh @ Dreamland]

Damn it, polygone.

Anyway, the options panel. Things it should contain.

THE

EXTERNAL

SPRITE

AND

IMAGE

EDITOR

NAMES

Just for a start.

Also, I'd not mind theme information, if that's not too tricky. You know, Windows look and feel shit.

[polygone]

+1 for theme options. I also want an option to not group similar events in the object editor.

I'm listing all the suggestion on the wiki as well: http://enigma-dev.org/docs/Wiki/Options_panel:Suggestions

I'll probably think of a load more before long, obviously there numerous options that should be added for joshedit. I doubt anyone really cares what it looks like, or the layout, it's only an options panel.

[Josh @ Dreamland]

Don't forget the JE options panel. It needs included.

[polygone]

OK, just remembered some options I want. I would like much better control over the enigma settings, with options to default load a specific settings file when opening a file type:

Default Settings: <file> (this settings file will always be opened upon LGM start/new game, when file is not given nothing changes)
GM6 Settings: <file> (this settings file will always be opened upon loading  gm6 file, when file is not given nothing changes)
.. etc for all the file types

It would also be nice to have a setting for which events.res file to use.

[IsmAvatar]

Actually, we planned to hard-code the settings so that:
Default: All options switched to the right.
Load a GM File: All options switch to the left.
Load an EGM File: All options loaded from file.

This will be a tricky one to implement since the load process for LGM-native files (GM*) is directly coded into LGM, so it's not something the Plugin can really respond to. There's ways around it, so that's what I'm going for - even if it means a slight modification to LGM's load process to allow better plugin access to it.

[polygone]

I definitely think it is a lot better to have control over it than have it hard-coded. I want control over what API's and extensions are set as well as those.

[Josh @ Dreamland]

IsmAvatar: I see what polygone is saying. I had requested to you at some point that we place those defaulted presets in a settings file somewhere.

I suppose we could have the UI allow you to set them, but that could get bloaty. Maybe we could just have a checkbox that says "Default GMK profile" and another that says "Default ENIGMA profile". When you toggle a checkbox, it checks if it matches either default profile and toggles those two checkboxes accordingly. When you check one of those two boxes, it asks you to confirm, and then overwrites the default. It'd be good to find some way of showing which boxes are mismatched between the default when you mouse over the checkbox, but that might be asking too much.

If you don't like that idea, another idea is to have it keep a collection of those "profiles" that the user can add to, manipulate, and choose from. Just a combo box for "Set as profile" which contains a list of all profiles and an option for "New..." which then prompts for a name; then another combo box for "Use profile" which contains the list.

[IsmAvatar]

When you toggle a checkbox

When you toggle a setting - I presume you meant. Using "checkbox" makes your sentence very confusing.
Initially I was just thinking of having a Button, instead of a checkbox.
The way you describe it, it sounds like a "Save Profile" and "Load Profile" button - if simplified to not traverse directories - would be a pretty good solution.

[Josh @ Dreamland]

Sounds good to me. Just don't overkill the UI; the reason I said combobox instead of button was so we didn't make the user move the mouse too much to pick a profile.

And yes, sorry; I did mean change a setting rather than toggle a checkbox there. Got ahead of myself.

[IsmAvatar]

I agree with not overkilling the UI, the combobox certainly sounds like another option - with "Custom" as one of the options that automatically selects if you change anything. The mouse reasoning is silly - it's not like the user's going to be changing the profile frequently.

[Josh @ Dreamland]

Sure, but in any case, it seems to me that if you can give it features as though it will be used frequently without making it as obtrusive as if it would be used that frequently, it's a good idea to do so.