1
1
Fork 0
mirror of https://github.com/FellippeHeitor/InForm.git synced 2025-01-15 11:59:34 +00:00
GUI engine and WYSIWYG interface designer for QB64
Find a file
FellippeHeitor 54cf8e368c #10: Allows setting the default button in a form at design time.
Right-clicking a button now offers the option to "Set as default button".
2018-03-11 21:37:38 -03:00
InForm #10: Allows setting the default button in a form at design time. 2018-03-11 21:37:38 -03:00
build.bat Improved support for ToggleSwitch control. 2018-01-23 23:02:07 -02:00
falcon.h Restructure. 2016-12-18 04:24:47 -02:00
LICENSE.md Create LICENSE.md 2018-01-10 18:36:37 -02:00
README.md Update README.md 2016-12-19 12:38:51 -02:00
setup_inform_lnx.sh Update Linux script (line endings). 2017-03-22 09:41:43 -03:00
setup_inform_macos.command Add setup scripts for macOS and Linux 2016-12-18 17:19:38 -02:00
UiEditor.exe #10: Allows setting the default button in a form at design time. 2018-03-11 21:37:38 -03:00

InForm

A GUI engine and WYSIWYG interface designer for QB64

Wiki: https://github.com/FellippeHeitor/InForm/wiki

Event-driven QB64 programs

InForm's main goal is to generate event-driven QB64 applications. This means that you design a graphical user interface with interactive controls and then write the code to respond to such controls once they are manipulated.

Workflow

After your form looks the way you want it to, click File -> Save to export its contents and generate a .bas source file. Three files are output:

  • .frmbin the binary form that can be later edited.

  • .frm a representation of the generated form in QB64 code. This can be edited in QB64 or any text editor later, if you want to adjust fine details.

  • .bas the actual program you will add your code to.

You add code to respond to events:

  • Click
  • MouseEnter/MouseLeave (hover)
  • FocusIn/FocusOut
  • MouseDown/MouseUp (events preceding a Click)
  • KeyPress
  • TextChanged (for text box controls)
  • ValueChanged (for track bars, lists and dropdown lists)

There are also events that occur in specific moments, to which you can respond/add code:

  • BeforeInit, triggered just before the form is shown.
  • OnLoad, triggered right after the form is first shown.
  • BeforeUpdateDisplay, triggered everytime the form is about to be repainted.
  • BeforeUnload, triggered when the user tries to close the program, either via clicking the window's X button, right click in the task bar -> Close or with Alt+F4 (Windows only).