Author Topic: EZGUI  (Read 18263 times)

0 Members and 3 Guests are viewing this topic.

JRS

  • Guest
EZGUI
« on: March 21, 2018, 04:14:05 PM »
Quote from: Chris Boss
You have been selected to get one of the FREE EZGUI 5.0 Professional licenses being offered.

Thanks Chris!

The plan is to use this copy of EZGUI to test under OxygenBasic and Script BASIC (via DLLC)

I will post my progress in this thread.



JRS

  • Guest
EZGUI
« Reply #1 on: March 23, 2018, 10:47:32 PM »
Hi Roland,

Thanks for the getting started with O2 GUI forms programming examples.

Where is the callback function return variable used?

I'm playing around with EZGUI.DLL and Chris has three defined callbacks that require function pointers passed to define them. How is that done in O2?


Arnold

  • Guest
Re: EZGUI
« Reply #2 on: March 24, 2018, 12:28:51 AM »
Hi John,

Charles has done many brilliant things in the accompanying include files. @Wndproc is provided in function MainWindow of WinUtil.inc. And of course there is also a basic Message Loop.

Roland
« Last Edit: March 24, 2018, 12:38:40 AM by Arnold »

JRS

  • Guest
Re: EZGUI
« Reply #3 on: March 24, 2018, 12:45:45 AM »
I think I'm going to use the same method for event handling in EZGUI as I did with IUP. Actually EZGUI will be easier as there are only 3 callback functions to support events.

Charles,

Is there a way I could create a virtual function with DLLC, get its function address pointer and pass it to EZGUI?
« Last Edit: March 24, 2018, 12:53:02 AM by John »

Charles Pegge

  • Guest
Re: EZGUI
« Reply #4 on: March 24, 2018, 02:39:47 AM »
Hi John,

I think it must be similar to handling callbacks in IUP. These are handled by virtual functions, which service the callbacks, and pass data back to SB. projectsC\ScriptBasic\IUP

Chris Boss

  • Guest
Re: EZGUI
« Reply #5 on: March 24, 2018, 08:31:29 AM »
A quick look at a GUI example in the examples folder of Oxygen, you simply use the @ character in front of the procedure or function name.

For example a window procedure called WinProc would use @WinProc for a pointer.

In PB:    CODEPTR(WinProc)

In O2:   @WinProc

In the ezwmain50.inc file of EZGUI you would change the three code pointer parameters for the EZ_GuiRun call from:

...      CODEPTR(EZ_Main), CODEPTR(EZ_Events), CODEPTR(EZ_DesignWindow)   ...

...      @EZ_Main,  @EZ_Events,  @EZ_DesignWindow   ...

There are other parameters in the EZ_GuiRun call and some may need to be modified to match O2 syntax, but the above solves the code pointer ones.

Does O2 have a MACRO command ?

One could write a Macro for any conversions from PB to O2.



JRS

  • Guest
Re: EZGUI
« Reply #6 on: March 24, 2018, 09:21:22 AM »
Thanks Chris!

That was very helpful. I hope to have a Script BASIC / O2 EZGUI example posted soon.

Quote
Does O2 have a MACRO command?

Yes.

My plan is to let O2 (DLLC) (pre)process the raw EZGUI events at compiler code generation speeds and pass it off to Script BASIC once the event has been identified.

Chris Boss

  • Guest
Re: EZGUI
« Reply #7 on: March 24, 2018, 10:00:57 AM »
If you can get EZGUI to work with O2 and ScriptBasic, I might consider making a freeware version with less features, kind of like an EZGUI Standard version. That way more would get to use it and then if they like it consider purchasing the Pro version. EZGUI is so feature rich now, that even a Free/Standard version would provide significant features.

Send me any examples of using EZGUI with O2 or ScriptBasic, so I can do some testing with them.

JRS

  • Guest
Re: EZGUI
« Reply #8 on: March 24, 2018, 10:46:51 AM »
My suggestion is display a nag unregistered message if the EZGUI init is done with null values.

chrisc

  • Guest
Re: EZGUI
« Reply #9 on: March 24, 2018, 11:38:47 AM »
Yes Chris Boss
You make our day, Sir

Please develop your EzGui program for O2 and make able to emit code in O2

JRS

  • Guest
Re: EZGUI
« Reply #10 on: March 24, 2018, 12:29:22 PM »
There is money to pay for add-ons if the compiler is FREE.

Have we forgotten the after market of VB classic controls and widgets? O2 could bring that back.

Charles Pegge

  • Guest
Re: EZGUI
« Reply #11 on: March 24, 2018, 01:55:48 PM »
O2 will support any standard DLL. Is EZGUI limited to 32bit at present, Chris?

The main task in supporting ScriptBasic would be to manage all the messages in a form that a script engine can cope with, filtering out mouse-move messages, and storing position, for instance.

jcfuller

  • Guest
Re: EZGUI
« Reply #12 on: March 24, 2018, 02:32:50 PM »
Charles,
  It's written in PowerBASIC I believe so it will always be 32bit.
Nort much use to me as I haven't done 32bit in years.

James


JRS

  • Guest
Re: EZGUI
« Reply #13 on: March 24, 2018, 08:46:24 PM »
Quote from: Charles
The main task in supporting ScriptBasic would be to manage all the messages in a form that a script engine can cope with, filtering out mouse-move messages, and storing position, for instance.

My goal with message loops and event handlers is to have them only return events I have defined before starting the pump.

JRS

  • Guest
Re: EZGUI
« Reply #14 on: March 24, 2018, 08:49:12 PM »
Charles,
  It's written in PowerBASIC I believe so it will always be 32bit.
Nort much use to me as I haven't done 32bit in years.

James

My hope is Chris hasn't been idle just because he was locked in a 32 bit box and has investigated what needs to change in EZGUI to go to 64 bit.