SprigForm (WIP)

[SpriggsySpriggs]

Won't be posting code just yet, but I did want to share my simple test of a combo box from the Win32 API. I'm trying to make a nice GUI forms library that will use as many Win32 controls as I can, and be able to support multiple windows without having to use multiple executables or fake the windows like other GUI libraries do. Ignore the theming of the test, as I am running a 95 theme on my computer and it messes with everything. Don't expect code for a while, but I might occasionally post a GIF or screenshot.

   

[TempodiBasic]

WoW, cool Zack!
This remembers me the time of win95 and Windows Framework used to build Notepad!

[SpriggsySpriggs]

Tried out a rich edit control. Very neat. I'll have to tinker with more features of that control. But you can paste in images and even resize them.

   

[SpriggsySpriggs]

And here is a test showing multiple windows. The QB64 window, which is the parent to the first Win32 window, which is the parent to the child Win32 window. Notice how closing the child does not kill the parent and how it does not end the program. Closing the parent Win32 window kills the child as well. Both windows can have their own control children as well.

   

[bplus]

Multiple windows is something alright!

[SpriggsySpriggs]

Now here is multiple windows with their own controls and different fonts. I did a simple setup of a combo box, edit box, and a button. Notice how the program handles the inputs from both windows without confusion.

   

[Pete]

You'd have a winner on your hands by just making it possible to run QB64 cod in a given Win32 child window. That would be a neat library on its own. but it would probably require two mouse libraries.

I've tried a lot of this stuff, including the multiple window thing using two or more exe files, but also with a single file and the PITA it is to code for all the overlap, focus, etc. In other words making a movable popup as smooth is QB64 a it is in Win32 is not quite possible and when you add overlap checking, focus checking, etc. it gets even less responsive. Hardware acceleration gives nicer results than standard graphics or text, but even so, if you really want to go child window happy, you need Win32 or at least an hefty increase in the child tax credit!

I'll +2 this one ahead of the code. Nice demo posts, btw.

Pete

[SpriggsySpriggs]

You'd have a winner on your hands by just making it possible to run QB64 cod in a given Win32 child window. That would be a neat library on its own. but it would probably require two mouse libraries.

Two mouse libraries? Why's that? And do you mean like interpreting or do you mean calling QB64 functions from the children and displaying the output in the windows?

I'll +2 this one ahead of the code. Nice demo posts, btw.

And muchas gracias!

[Pete]

I look forward to importing your Win32 code, and deporting your muchas gracias!

A mouse library from the Win32 child windows, and a qb64 mouse routine for the programs running inside the child window. I know, they could be controlled by the same win32 mouse routine as well, but I was thinking more along the lines of pure QB64 routines running inside a Win32 child window. I'm thinking I did a similar routine a few years ago. When the mouse pointer went outside the window, my Win32 mouse routine took over. I know, most folks experiment with drugs, but I do it with code. Now if you will excuse me, I have to go huff some FreeBasic. It won't kill you like fentanyl, but it does make you wish you were dead.

Pete

[Unseen Machine]

I had SFML making as many windows as you wanted a decade ago but they inherently needed their own functions (couldn't use Qb64's) to get input etc...so i never pushed it now this though...seems i can have an active Debug window whilst running a program! ROCK AND ROLL!

PUSH THOSE LIMITS BABY!