At this time there is an automatic generated event-function (loop) if activated.
Good would be if this could be bindevents, if possible with the option to choose possible events and procedure name to jump to on event.
Like this:
Button Gadget.
Button Name: "Test"
Bind Event "Left Click" -> Procedure "Button_Test_LeftClick()"
Bind Event "Right Click" -> Procedure "Button_Test_RightClick()"
(Procedure Names should be automatic offered by Button Name and event Type - would be much easier!
Dropdown List of procedures would maybe just a nice extra.)
Ultimate would be if there would be a small Button and if pressed, IDE opens a specific Codefile, Cursor jumps to end
and prints Procedure Name. But no automatic changes (to easy add parameters manually or something else)
Bindevents in a Procedure in another Codefile, autamatic generated on every change.
That would be similar to VBA, and a big advantage for fast GUI designing/programming.
Thank You.
Automated BindEvents Procedure!
-
OnErrorGotoTrashcan
- New User
- Posts: 4
- Joined: Wed Dec 04, 2013 11:44 am
Automated BindEvents Procedure!
I got very bored and depressed, so I went and plugged myself in to its external computer feed. I talked to the computer at great length and explained my view of the Universe to it.
And what happened?
It committed suicide. (Marvin)
And what happened?
It committed suicide. (Marvin)
-
Lothar Schirm
- User
- Posts: 54
- Joined: Mon Nov 26, 2012 4:57 pm
Re: Automated BindEvents Procedure!
I agree with these ideas. I think we need a more automatic generation of event procedures in this way or similarly. Actually, working with projects and the Form Designer requires a lot of manual actions:
- creating a project folder (not mandatory, but useful for larger projects)
- creating "IncludeFile" statements for each generated form (.pbf file) within the main file (.pb file)
- writing event procedures manually into the main file for each gadget, if needed
- selecting for each gadget within a form an event procedure from the main file, if needed.
The IDE can be configured to use a colour scheme like Visual Studio. It would be nice if the IDE together with the Form Designer would also offer some user friendly features similiar to Visual Studio.
For instance, have a look at the FireFly Visual Designer for FreeBASIC (freeware!). Its use is very comfortable, like Visual Basic. It does all these things automatically. I only do not use it regularly because it generates a lot of additional files and horrible WinApi code in the main file. But the PB team should consider that they are in competition with other software developers for GUI RAD systems.
- creating a project folder (not mandatory, but useful for larger projects)
- creating "IncludeFile" statements for each generated form (.pbf file) within the main file (.pb file)
- writing event procedures manually into the main file for each gadget, if needed
- selecting for each gadget within a form an event procedure from the main file, if needed.
The IDE can be configured to use a colour scheme like Visual Studio. It would be nice if the IDE together with the Form Designer would also offer some user friendly features similiar to Visual Studio.
For instance, have a look at the FireFly Visual Designer for FreeBASIC (freeware!). Its use is very comfortable, like Visual Basic. It does all these things automatically. I only do not use it regularly because it generates a lot of additional files and horrible WinApi code in the main file. But the PB team should consider that they are in competition with other software developers for GUI RAD systems.