QB64.org Forum

QB64 Team Software => InForm Discussion => Topic started by: TempodiBasic on August 29, 2018, 06:16:07 pm

Title: [InForm] incompatibility Inform vs QB64 Variable naming rules
Post by: TempodiBasic on August 29, 2018, 06:16:07 pm

Hi Fellippe

while I'm trying to get an alternative method to manage input keyboard to the goal (calculator) of Terry
I have fallen in this issue...

If I set Caption of a Button like a number.... Inform has coded that number as name of a variable LONG for ID of that item.
But as soon as the code (.BAS) is loaded in QB64 ide it halts me with warning Invalid variable name on line....

Here is .BAS

Code: QB64: [Select]

1. ': This program uses
2. ': InForm - GUI library for QB64 - Beta version 7
3. ': Fellippe Heitor, 2016-2018 - fellippe@qb64.org - @fellippeheitor
4. ': https://github.com/FellippeHeitor/InForm
5. '-----------------------------------------------------------
6.  
7. ': Controls' IDs: ------------------------------------------------------------------
8. DIM SHARED Numbers AS LONG
9. DIM SHARED PressNumberButtonLB AS LONG
10. DIM SHARED PressedNumberButtonLB AS LONG
11. DIM SHARED 1BT AS LONG
12. DIM SHARED 2BT AS LONG
13. DIM SHARED 3BT AS LONG
14. DIM SHARED 4BT AS LONG
15. DIM SHARED 5BT AS LONG
16.  
17. ': External modules: ---------------------------------------------------------------
18. '$INCLUDE:'InForm\InForm.ui'
19. '$INCLUDE:'InForm\xp.uitheme'
20. '$INCLUDE:'Numbers.frm'
21.  
22. ': Event procedures: ---------------------------------------------------------------
23. SUB __UI_BeforeInit
24.  
25. END SUB
26.  
27. SUB __UI_OnLoad
28.  
29. END SUB
30.  
31. SUB __UI_BeforeUpdateDisplay
32.     'This event occurs at approximately 30 frames per second.
33.     'You can change the update frequency by calling SetFrameRate DesiredRate%
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.  
41. END SUB
42.  
43. SUB __UI_Click (id AS LONG)
44.     SELECT CASE id
45.         CASE Numbers
46.  
47.         CASE PressNumberButtonLB
48.  
49.         CASE PressedNumberButtonLB
50.  
51.         CASE 1BT
52.  
53.         CASE 2BT
54.  
55.         CASE 3BT
56.  
57.         CASE 4BT
58.  
59.         CASE 5BT
60.  
61.     END SELECT
62. END SUB
63.  
64. SUB __UI_MouseEnter (id AS LONG)
65.     SELECT CASE id
66.         CASE Numbers
67.  
68.         CASE PressNumberButtonLB
69.  
70.         CASE PressedNumberButtonLB
71.  
72.         CASE 1BT
73.  
74.         CASE 2BT
75.  
76.         CASE 3BT
77.  
78.         CASE 4BT
79.  
80.         CASE 5BT
81.  
82.     END SELECT
83. END SUB
84.  
85. SUB __UI_MouseLeave (id AS LONG)
86.     SELECT CASE id
87.         CASE Numbers
88.  
89.         CASE PressNumberButtonLB
90.  
91.         CASE PressedNumberButtonLB
92.  
93.         CASE 1BT
94.  
95.         CASE 2BT
96.  
97.         CASE 3BT
98.  
99.         CASE 4BT
100.  
101.         CASE 5BT
102.  
103.     END SELECT
104. END SUB
105.  
106. SUB __UI_FocusIn (id AS LONG)
107.     SELECT CASE id
108.         CASE 1BT
109.  
110.         CASE 2BT
111.  
112.         CASE 3BT
113.  
114.         CASE 4BT
115.  
116.         CASE 5BT
117.  
118.     END SELECT
119. END SUB
120.  
121. SUB __UI_FocusOut (id AS LONG)
122.     'This event occurs right before a control loses focus.
123.     'To prevent a control from losing focus, set __UI_KeepFocus = True below.
124.     SELECT CASE id
125.         CASE 1BT
126.  
127.         CASE 2BT
128.  
129.         CASE 3BT
130.  
131.         CASE 4BT
132.  
133.         CASE 5BT
134.  
135.     END SELECT
136. END SUB
137.  
138. SUB __UI_MouseDown (id AS LONG)
139.     SELECT CASE id
140.         CASE Numbers
141.  
142.         CASE PressNumberButtonLB
143.  
144.         CASE PressedNumberButtonLB
145.  
146.         CASE 1BT
147.  
148.         CASE 2BT
149.  
150.         CASE 3BT
151.  
152.         CASE 4BT
153.  
154.         CASE 5BT
155.  
156.     END SELECT
157. END SUB
158.  
159. SUB __UI_MouseUp (id AS LONG)
160.     SELECT CASE id
161.         CASE Numbers
162.  
163.         CASE PressNumberButtonLB
164.  
165.         CASE PressedNumberButtonLB
166.  
167.         CASE 1BT
168.  
169.         CASE 2BT
170.  
171.         CASE 3BT
172.  
173.         CASE 4BT
174.  
175.         CASE 5BT
176.  
177.     END SELECT
178. END SUB
179.  
180. SUB __UI_KeyPress (id AS LONG)
181.     'When this event is fired, __UI_KeyHit will contain the code of the key hit.
182.     'You can change it and even cancel it by making it = 0
183.     SELECT CASE id
184.         CASE 1BT
185.  
186.         CASE 2BT
187.  
188.         CASE 3BT
189.  
190.         CASE 4BT
191.  
192.         CASE 5BT
193.  
194.     END SELECT
195. END SUB
196.  
197. SUB __UI_TextChanged (id AS LONG)
198.     SELECT CASE id
199.     END SELECT
200. END SUB
201.  
202. SUB __UI_ValueChanged (id AS LONG)
203.     SELECT CASE id
204.     END SELECT
205. END SUB
206.  
207. SUB __UI_FormResized
208.  
209. END SUB
210.  
211.  

So, to continue in my coding I must rename the name of items (in this case of Buttons)

theorically the MakeNameOfItem of InForm, that usually makes name equal to Caption of the item, could have a flag option like CaptionName (that I find very useful) and StandardName (that was NameItemNumberItem i.e. Label1). And if CaptionName is active the MakeNameOfItem could check if the first character is ok or add in lowercase the item string (i.e.  1BT becomes bt1BT,  1LB becomes lb1LB) like I have done manually in this example that I'll post for another issue in another thread.

Thanks to read and to try

Title: Re: [InForm] incompatibility Inform vs QB64 Variable naming rules
Post by: FellippeHeitor on August 29, 2018, 06:47:06 pm

I tried to foolproof the autonaming routine but that case escaped me. I will review it before the next beta is released, thanks for reporting.

Title: Re: [InForm] incompatibility Inform vs QB64 Variable naming rules
Post by: FellippeHeitor on August 30, 2018, 01:45:31 pm

I went on to try to replicate the error with InForm's editor and I'm baffled, TempodiBasic.

When I try to change the caption of a button to "1", the autoname feature renames the control as "BT", not "1BT".

Then I went on to try to manually rename the control (not the caption) to "1BT". InForm didn't let me.

My question is: How were you able to name those controls with a number as the first character?

Title: Re: [InForm] incompatibility Inform vs QB64 Variable naming rules
Post by: FellippeHeitor on August 30, 2018, 02:58:24 pm

Went back to Beta 6 and couldn't reproduce the issue either. Please let me know how to reproduce it as soon as you can.

Title: Re: [InForm] incompatibility Inform vs QB64 Variable naming rules
Post by: TempodiBasic on August 31, 2018, 04:22:45 am

Hi Fellippe

1. Thanks for time and attentions to my communications
2. You are right and so I'm right :-) Win-Win
 2.1 Why? If you try to rename the item_control starting with a number You cannot do this!
 2.2 If you do like me: renaming the item_control starting with & because I want that the number is a Hotkey to press button, now yu get my results.

Dear Fellippe I attach a image file with result and InForm version

Good Coding

Title: Re: [InForm] incompatibility Inform vs QB64 Variable naming rules
Post by: FellippeHeitor on August 31, 2018, 07:16:02 am

Ah! Mystery solved. Thank you!

Text Only | Text with Attachments