In FF35 the "Minimum Operating System to Support" can be set.
What does that do?
If Windows Server 2003 is selected and a user tries to run on Windows XP do they
get a message? What happens?
In general what should "Minimum Operation System" be set to?
Where should I store Includes INC for functions in other DLLs that I might use?
Should I put them in with JoseAPI or should I create my own \Include directory?
How does the Resize Rules work? I have tried them with Jose's OCXactiveX control (webbrowser) and it didn't do anything. Is there an example program that demostrates that feature?
I think you are talking minimum supported OS .. so for example.
2k xp win7 and you selected xp, then xp and win 7 are supported , but not 2k ...
The resizing might not be that obvious at the beginning, but here is an example I would claim to be rather typical
and hopefully making it a little more clear without "deep" explanations.
It's desirable to have the "square-thingy" scale, but have the buttons still stay as they do in relation to the rest.
In combination with some minimum size restrictions for the form, this would behave perfectly logical.
Edit: There is something preventing the resize feature to work as supposed on the AxtiveX container, but I don't
know what that would be without investigating. Not sure I'm gonna do that though.
Your INC files probably should go in the FF_AppStart
Quote from: Marty Francom on November 09, 2011, 07:39:45 PM
In FF35 the "Minimum Operating System to Support" can be set.
What does that do?
If Windows Server 2003 is selected and a user tries to run on Windows XP do they
get a message? What happens?
In general what should "Minimum Operation System" be set to?
Where should I store Includes INC for functions in other DLLs that I might use?
Should I put them in with JoseAPI or should I create my own \Include directory?
How does the Resize Rules work? I have tried them with Jose's OCXactiveX control (webbrowser) and it didn't do anything. Is there an example program that demostrates that feature?
I opted to keep Jose's files and other includes a little separate as the API includes are "frequently" updated and I prefer emptying and replacing the contents of the folder. As for the other sparse includes, I'd like to be a little in control and have that folder somewhat clear.
My structure, based on having almost all applications on a separate data disk. Separate from the OS disk/partition that is.
D:\dev\firefly ...
D:\dev\powerbasic ...
D:\dev\other_app's
D:\dev\Includes\ â€" here is my handful of includes and Jose's help-file (Wrapper Reference)
D:\dev\Includes\WinAPI II â€" here are Jose's (latest) includes
QuoteIn general what should "Minimum Operation System" be set to?
I have no recollection of that making any difference when it comes to running an application with minimum requirements set to w7 and running it on XP. It might be some kind of flag that installers would pick up on?
At some point I guess Paul will drop by to clarify the real inner workings of that setting.
Quote from: James Padgett on November 09, 2011, 09:14:48 PM
I think you are talking minimum supported OS .. so for example.
2k xp win7 and you selected xp, then xp and win 7 are supported , but not 2k ...
Ok, say it's set to xp. What happen when someone tries to run it on 2k ?
Do they get s message that says "No can do!" or something to that effect?
Haakon, that you for the example program. I will play with it to learn how to use that feature.
Quote
Ok, say it's set to xp. What happen when someone tries to run it on 2k ?
Do they get s message that says "No can do!" or something to that effect?
See #OPTION metastatement in the PB help file.