Hi all... i'll be developing this within a DLL as well so the functions are better equipped and made faster later.
However for now i'm going to develop this today within Pro and test on my Laptop which finally has a working demo of Pro on it
what i'm doing is creating a dpmfc.lib (renamed dba) that you include within projects, and then use the functions to develop your utility programs without much hassle
so windows, buttons, menus are all developed and setup for you and all you have to do is type say
if (mfcButton(x,y,sizex,sizey,text$))=1
goSub _action
endif
and et voila you have a working button, or a table menu setup in a way that you just input the data you wish to use for it.
unlike IronHoofs Visual DarkBasic - you don't plot out what your making in it (atleast not yet) you have to actually hard code it all. Hopefully the functions should be so simple to operate that it doesn't matter though
now i'd like everyones input on what they would prefer these functions to be named, because it'll really be a global thing and when the DLL is made they'll be named the same.
right now everything is called mfc[FunctionName]()
this is because basically Microsoft Foundation Classes are what give C++ users the windows native GUI functions.
as the complexity of this is going to go into being able to dock and undock windows (something which is a pain in the ass to code) ... different window styles for different options.
now i'll probably release something vaguely familiar tommorrow, and i'll compile 2 colour sets Windows.Clr and RavenTau.Clr - which will be Windows Classic and my own graphics stlye which was recently shown for a possible gui layout of gameMatrix.
also ... if anyone has any particular request for certain functions to be premade then i'll look into it later.
Currently what will be developed is ->
Text Buttons
Icon Buttons
Windows (using Icon Buttons)
Frame Dialogues
Drop-Down Menu's
Mouse Menu's (right-click)
Mouse Quick Names (eg, MB_OK makes a button with okay on it)
Keyboard Accelerator (shortcut array functions)
Combo Menu's
Status Bar
Tab Menu's
Roll-Out Menu's
Rich Text Dialouge Type
Standard Text Dialouge Type
Render Window Type
Containment Menu
Radio Buttons
Check Buttons
Now believe it or not the hard part isn't getting each of these working ... the hard part is to make functions that can be seemlessly intertwined with each other
i will be adopting a C++ style of coding for this, for example
MessageBox( tool.nox, x,y, "Function Failed", "Error", "MB_OK() | MB_CANCEL(QUIT())"))
this will cause a windows style popup that won't allow the user to carryon unless they OK or CANCEL it...
It displays "Function Failed" where the error is and "Error" in the titlebar.
It's using a toolbar menu with no X quit feature.
If the user presses cancel it runs the QUIT() function which closes DBpro application
you'll be able to line up several functions in certain functions with the | "pipeline" symbol
the toolbar.noesc type actually simply points to a value which you could use yourself - but it is easier to use the descriptive function types
really would like to know what everyone else would like within this.

Anata aru kowagaru no watashi! http://members.lycos.co.uk/timesaga/darkbasic/gir.gif[/img]