QB64.org Forum

Active Forums => QB64 Discussion => Topic started by: Rich on January 23, 2020, 06:39:59 pm

Title: InForm Question
Post by: Rich on January 23, 2020, 06:39:59 pm

I am confused as to where to place my code after I have created and a form in Inform. There seems to be many places to put the code. Is there a template available to show what control subroutine (in QB64) relates to a specific control. I hope this makes some sense.

Title: Re: InForm Question
Post by: TempodiBasic on January 24, 2020, 04:36:07 pm

Hi Rich
in my little experience I can affirm that Inform follows the model of event programming....
so
1.you must divide your program in the events that happen
2. then you can decide where write and what  write

here just a dummy example/demonstration

Code: QB64: [Select]

1. ': This program uses
2. ': InForm - GUI library for QB64 - v1.1
3. ': Fellippe Heitor, 2016-2019 - fellippe@qb64.org - @fellippeheitor
4. ': https://github.com/FellippeHeitor/InForm
5. '-----------------------------------------------------------
6.  
7. ': Controls' IDs: ------------------------------------------------------------------
8. DIM SHARED Template AS LONG
9. DIM SHARED DoBT AS LONG
10. DIM SHARED QuitBT AS LONG
11. DIM SHARED OutputLB AS LONG
12. DIM SHARED InputTB AS LONG
13.  
14. ': External modules: ---------------------------------------------------------------
15. '$INCLUDE:'InForm\InForm.ui'
16. '$INCLUDE:'InForm\xp.uitheme'
17. '$INCLUDE:'Template.frm'
18.  
19. ': Event procedures: ---------------------------------------------------------------
20. SUB __UI_BeforeInit
21. 'here you can write all you need Before Initialization of Inform system
22. END SUB
23.  
24. SUB __UI_OnLoad
25. 'Here you can write all settings that are permanent at starting /and during the execution of program
26. ' and also all resources that you need to pre-load before your program starts
27. END SUB
28.  
29. SUB __UI_BeforeUpdateDisplay
30.     'This event occurs at approximately 30 frames per second.
31.     'You can change the update frequency by calling SetFrameRate DesiredRate%
32.  
33.  'here you can write all those actions that must be repeated in loop with 30 fps speed
34.  
35. END SUB
36.  
37. SUB __UI_BeforeUnload
38.     'If you set __UI_UnloadSignal = False here you can
39.     'cancel the user's request to close.
40. ' here you can FREE memory from data /images/sound etc OR perform emergency saving
41. END SUB
42.  
43. SUB __UI_Click (id AS LONG)
44. 'Here you can manage the click event
45. ' the pre_built Select Case let you distinguish among the different objects
46.     SELECT CASE id
47.         CASE Template
48.                  Text(InputTB) = ""
49.         CASE DoBT
50.                 Caption(OutputLB) = Text(InputTB)  
51.         CASE QuitBT
52.  
53.         CASE OutputLB
54.  
55.         CASE InputTB
56.  
57.     END SELECT
58. END SUB
59.  
60. SUB __UI_MouseEnter (id AS LONG)
61.     SELECT CASE id
62.         CASE Template
63.  
64.         CASE DoBT
65.  
66.         CASE QuitBT
67.  
68.         CASE OutputLB
69.  
70.         CASE InputTB
71.  
72.     END SELECT
73. END SUB
74.  
75. SUB __UI_MouseLeave (id AS LONG)
76.     SELECT CASE id
77.         CASE Template
78.  
79.         CASE DoBT
80.  
81.         CASE QuitBT
82.  
83.         CASE OutputLB
84.  
85.         CASE InputTB
86.  
87.     END SELECT
88. END SUB
89.  
90. SUB __UI_FocusIn (id AS LONG)
91.     SELECT CASE id
92.         CASE DoBT
93.  
94.         CASE QuitBT
95.  
96.         CASE InputTB
97.  
98.     END SELECT
99. END SUB
100.  
101. SUB __UI_FocusOut (id AS LONG)
102.     'This event occurs right before a control loses focus.
103.     'To prevent a control from losing focus, set __UI_KeepFocus = True below.
104.     SELECT CASE id
105.         CASE DoBT
106.  
107.         CASE QuitBT
108.  
109.         CASE InputTB
110.  
111.     END SELECT
112. END SUB
113.  
114. SUB __UI_MouseDown (id AS LONG)
115.     SELECT CASE id
116.         CASE Template
117.  
118.         CASE DoBT
119.  
120.         CASE QuitBT
121.  
122.         CASE OutputLB
123.  
124.         CASE InputTB
125.  
126.     END SELECT
127. END SUB
128.  
129. SUB __UI_MouseUp (id AS LONG)
130.     SELECT CASE id
131.         CASE Template
132.                  Text(InputTB) = ""  
133.         CASE DoBT
134.                  Caption(OutputLB) = Text(InputTB)
135.         CASE QuitBT
136.                  SYSTEM
137.         CASE OutputLB
138.  
139.         CASE InputTB
140.  
141.     END SELECT
142. END SUB
143.  
144. SUB __UI_KeyPress (id AS LONG)
145.     'When this event is fired, __UI_KeyHit will contain the code of the key hit.
146.     'You can change it and even cancel it by making it = 0
147.     SELECT CASE id
148.         CASE DoBT
149.  
150.         CASE QuitBT
151.  
152.         CASE InputTB
153.  
154.     END SELECT
155. END SUB
156.  
157. SUB __UI_TextChanged (id AS LONG)
158.     SELECT CASE id
159.         CASE InputTB
160.  
161.     END SELECT
162. END SUB
163.  
164. SUB __UI_ValueChanged (id AS LONG)
165.     SELECT CASE id
166.     END SELECT
167. END SUB
168.  
169. SUB __UI_FormResized
170.  
171. END SUB
172.  
173.  

Title: Re: InForm Question
Post by: FellippeHeitor on January 24, 2020, 05:27:04 pm

As TempodiBasic exemplified, the .bas file that InForm saves is your template. Each SUB is an event (Click, OnLoad, ValueChanged, etc) and in each sub you’ll find your controls’ name to write code for.

Code: QB64: [Select]

1.  SUB __UI_Click (id AS LONG)
2.     SELECT CASE id
3.         CASE control1
4.                  'Enter code here for when control1 is clicked
5.         CASE control2
6.                  'Enter code here for when control2 is clicked
7.         CASE control3
8.                  'Enter code here for when control3 is clicked and etc
9.     END SELECT
10. END SUB

Title: Re: InForm Question
Post by: Rich on January 27, 2020, 10:00:53 am

Thank you!

Text Only | Text with Attachments