Sounds great. Is there any source code available for that?
Both IO and IOEx have a different system that needs an INI file to read what controls the user want. But both of them need a program resource rectangle to work (which is a huge limitation).
It is with the NSIS distribution, so you have to download NSIS
to get it.InstallOptionsEx
I added more controls, more flags, a much better notification system, font and color change on the page itself, tooltips (basic)... Unfortunately, it's on beta, so no examples are available (use IO's), and probably there has bugs.
Are these different enough from each other two have two separate controls, or should they be combined into one?
DateTime is a special ComboBox or Edit w/ UpDown control in which the date and time can be changed (See Date and Time Properties for example). If it's a ComboBox, when you click on the arrow, it shows a month calendar, just like the next control I'm going to talk about. You don't need to separate this control into two because it doesn't lose most of its funcionality when changing between "ComboBox" and "Edit w/ UpDown" modes.
MonthCalendar is just a month calendar where you select the prefered date. Nothing more.
Also, I wonder how tab order is defined... obviously it mirrors the order in which the controls were created.. but I suspect it has to do with which control is "top", which might in turn be all based on Z-order?
Hmm... focused... Only if you use FindWindow. This way it's all organized like you said.
Are you saying that the translation from CR+LF to plain LF is a good idea for the above controls?
Just forget this one, I sometimes don't read everything of a post correctly.
To clarify about GUI shows, I changed a little bit my idea because I forgot about "Control, Show" (thanks, Rajat). It made life easier:
First GUI show:
controls for a "Gui, Show". No controls reserved are affected by "Control" command.
After first GUI show:
- All controls that are added to a GUI should be hidden
by default. Then if you want to show only one control, use "Control, Show". If you want to show all controls at once, use "Gui, Show".
It's probably not documented anywhere yet, but windows beyond the first use a number prefix for their automatic labels. Examples:
Hmmmmm.... It would be difficult to differenciate several GUI's by their numbers... You could do this based on this syntax:
GUIName = the name set when that GUI was created
ControlType = all those controls types I mentioned before
ControlName = the name set when that control was created
Action = what user did to the control
(GUI is the GUI itself - it doesn't have a name because the name would be the same as GUIName)