QB64.org Forum

QB64 Team Software => InForm Discussion => Topic started by: Qwerkey on September 20, 2018, 06:14:09 am

Title: Mastering InForm: Click Response for Controls and for Screen Incompatibility
Post by: Qwerkey on September 20, 2018, 06:14:09 am

I am creating an InForm Mahjong Game (an Update of my existing program to InForm), and using hardware images put to the Form to display the Mahjong board and tiles.  So the game requires that you can click on the screen (as normal) to manipulate the tiles and also to click on the buttons to get other functions.  What I am finding is that you can either click on the screen or click on the buttons, but not both.  Running the program “QB64Mahjong.bas”, first you have to click on the button labelled “Start” and then click on the displayed Mouse with normal and then opposite mouse buttons (this is a routine that will set the program to know which buttons to react to in the running program – this routine is not yet implemented).  Then the tiles are displayed and you can click on appropriate tiles to match them.  However, none of the Buttons (Save/NewGame/Exit) are clickable until Esc is pressed.  Then the buttons are clickable but then the Mahjong game has stopped.

Am I able to allow both types of clicking at the same time?  Richard

Title: Re: Mastering InForm: Click Response for Controls and for Screen Incompatibility
Post by: FellippeHeitor on September 20, 2018, 03:26:33 pm

You should not be polling mouse data yourself, as InForm already does that in the background.

Your clicks should be processed in the __UI_Click event, reacting to the form's ID. Then you read __UI_MouseLeft and __UI_MouseTop.

Try running this example code. It's an empty form and each click on the form's surface will create a new button:

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 ClickMEform AS LONG
9.  
10. ': External modules: ---------------------------------------------------------------
11. '$INCLUDE:'InForm\InForm.ui'
12. '$INCLUDE:'InForm\xp.uitheme'
13.  
14. ': Form: ---------------------------------------------------------------------------
15. SUB __UI_LoadForm
16.  
17.     DIM __UI_NewID AS LONG
18.  
19.     __UI_NewID = __UI_NewControl(__UI_Type_Form, "ClickMEform", 392, 478, 0, 0, 0)
20.     SetCaption __UI_NewID, "ClickMEform"
21.     Control(__UI_NewID).Font = SetFont("segoeui.ttf", 12)
22.  
23. END SUB
24.  
25. SUB __UI_AssignIDs
26.     ClickMEform = __UI_GetID("ClickMEform")
27. END SUB
28.  
29. ': Event procedures: ---------------------------------------------------------------
30. SUB __UI_BeforeInit
31.  
32. END SUB
33.  
34. SUB __UI_OnLoad
35.  
36. END SUB
37.  
38. SUB __UI_BeforeUpdateDisplay
39.     'This event occurs at approximately 30 frames per second.
40.     'You can change the update frequency by calling SetFrameRate DesiredRate%
41.  
42. END SUB
43.  
44. SUB __UI_BeforeUnload
45.     'If you set __UI_UnloadSignal = False here you can
46.     'cancel the user's request to close.
47.  
48. END SUB
49.  
50. SUB __UI_Click (id AS LONG)
51.     SELECT CASE id
52.         CASE ClickMEform
53.             temp = __UI_NewControl(__UI_Type_Button, "", 20, 20, __UI_MouseLeft, __UI_MouseTop, 0)
54.     END SELECT
55. END SUB
56.  
57. SUB __UI_MouseEnter (id AS LONG)
58.     SELECT CASE id
59.         CASE ClickMEform
60.  
61.     END SELECT
62. END SUB
63.  
64. SUB __UI_MouseLeave (id AS LONG)
65.     SELECT CASE id
66.         CASE ClickMEform
67.  
68.     END SELECT
69. END SUB
70.  
71. SUB __UI_FocusIn (id AS LONG)
72.     SELECT CASE id
73.     END SELECT
74. END SUB
75.  
76. SUB __UI_FocusOut (id AS LONG)
77.     'This event occurs right before a control loses focus.
78.     'To prevent a control from losing focus, set __UI_KeepFocus = True below.
79.     SELECT CASE id
80.     END SELECT
81. END SUB
82.  
83. SUB __UI_MouseDown (id AS LONG)
84.     SELECT CASE id
85.         CASE ClickMEform
86.  
87.     END SELECT
88. END SUB
89.  
90. SUB __UI_MouseUp (id AS LONG)
91.     SELECT CASE id
92.         CASE ClickMEform
93.  
94.     END SELECT
95. END SUB
96.  
97. SUB __UI_KeyPress (id AS LONG)
98.     'When this event is fired, __UI_KeyHit will contain the code of the key hit.
99.     'You can change it and even cancel it by making it = 0
100.     SELECT CASE id
101.     END SELECT
102. END SUB
103.  
104. SUB __UI_TextChanged (id AS LONG)
105.     SELECT CASE id
106.     END SELECT
107. END SUB
108.  
109. SUB __UI_ValueChanged (id AS LONG)
110.     SELECT CASE id
111.     END SELECT
112. END SUB
113.  
114. SUB __UI_FormResized
115.  
116. END SUB
117.  

Title: Re: Mastering InForm: Click Response for Controls and for Screen Incompatibility
Post by: Qwerkey on September 21, 2018, 05:31:26 am

Oh, I hadn't appreciated that you can't do normal Mouse polling as well as InForm's Mouse control.  As you can use INKEY$ as well as __UI_KeyHit, I was assuming a similar thing for the Mouse.

My program requires sampling the cursor position continuously without any Click events, to get and use _MOUSEX & _MOUSEY.  The only InForm Mouse procedures (?) are __UI_MouseUp/Down & __UI_MouseEnter/Leave.  Am I allowed to sample _MOUSEINPUT and get _MOUSEX & _MOUSEY?  What are __UI_MouseLeft & __UI_MouseTop? This would imply MouseWidth & MouseHeight???

Also, the program (as is) uses opposite Mouse Button Click for an Undo routine.  Is this allowed in InForm (I don't see any Wiki on it)?  If not allowed, I'd have to have another Button Control for Undo which would be acceptable.

Please forgive the level of ignorance!  Richard

Title: Re: Mastering InForm: Click Response for Controls and for Screen Incompatibility
Post by: Qwerkey on September 21, 2018, 05:48:59 am

Quote from: Qwerkey on September 21, 2018, 05:31:26 am

Am I allowed to sample _MOUSEINPUT and get _MOUSEX & _MOUSEY?  What are __UI_MouseLeft & __UI_MouseTop? This would imply MouseWidth & MouseHeight???

Oops! I've answered that myself.  Just tried commenting out all WHILE _MOUSEINPUT loops and getting __UI_MouseLeft & __UI_MouseTop directly - they're exactly equivalent to _MOUSEX & _MOUSEY and the program no longer latches up the ButtonControls.

So, all I need now is Opposite Mouse Button Click.  Richard

Title: Re: Mastering InForm: Click Response for Controls and for Screen Incompatibility
Post by: FellippeHeitor on September 21, 2018, 08:53:11 am

Use __UI_MouseButton1 and __UI_MouseButton2.

Try this: Left click to add a button, Right click to add a ToggleSwitch:

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 ClickMEform AS LONG
9.  
10. ': External modules: ---------------------------------------------------------------
11. '$INCLUDE:'InForm\InForm.ui'
12. '$INCLUDE:'InForm\xp.uitheme'
13.  
14. ': Form: ---------------------------------------------------------------------------
15. SUB __UI_LoadForm
16.  
17.     DIM __UI_NewID AS LONG
18.  
19.     __UI_NewID = __UI_NewControl(__UI_Type_Form, "ClickMEform", 392, 478, 0, 0, 0)
20.     SetCaption __UI_NewID, "ClickMEform"
21.     Control(__UI_NewID).Font = SetFont("segoeui.ttf", 12)
22.  
23. END SUB
24.  
25. SUB __UI_AssignIDs
26.     ClickMEform = __UI_GetID("ClickMEform")
27. END SUB
28.  
29. ': Event procedures: ---------------------------------------------------------------
30. SUB __UI_BeforeInit
31.  
32. END SUB
33.  
34. SUB __UI_OnLoad
35.  
36. END SUB
37.  
38. SUB __UI_BeforeUpdateDisplay
39.     'This event occurs at approximately 30 frames per second.
40.     'You can change the update frequency by calling SetFrameRate DesiredRate%
41.  
42.     IF __UI_MouseButton1 THEN
43.         temp = __UI_NewControl(__UI_Type_Button, "", 20, 20, __UI_MouseLeft, __UI_MouseTop, 0)
44.         DO WHILE __UI_MouseButton1: _LIMIT 30: LOOP
45.         Caption(__UI_FormID) = STR$(temp)
46.     ELSEIF __UI_MouseButton2 THEN
47.         temp = __UI_NewControl(__UI_Type_ToggleSwitch, "", 20, 20, __UI_MouseLeft, __UI_MouseTop, 0)
48.         DO WHILE __UI_MouseButton2: _LIMIT 30: LOOP
49.         Caption(__UI_FormID) = STR$(temp)
50.     END IF
51.  
52. END SUB
53.  
54. SUB __UI_BeforeUnload
55.     'If you set __UI_UnloadSignal = False here you can
56.     'cancel the user's request to close.
57.  
58. END SUB
59.  
60. SUB __UI_Click (id AS LONG)
61.     SELECT CASE id
62.         CASE ClickMEform
63.  
64.     END SELECT
65. END SUB
66.  
67. SUB __UI_MouseEnter (id AS LONG)
68.     SELECT CASE id
69.         CASE ClickMEform
70.  
71.     END SELECT
72. END SUB
73.  
74. SUB __UI_MouseLeave (id AS LONG)
75.     SELECT CASE id
76.         CASE ClickMEform
77.  
78.     END SELECT
79. END SUB
80.  
81. SUB __UI_FocusIn (id AS LONG)
82.     SELECT CASE id
83.     END SELECT
84. END SUB
85.  
86. SUB __UI_FocusOut (id AS LONG)
87.     'This event occurs right before a control loses focus.
88.     'To prevent a control from losing focus, set __UI_KeepFocus = True below.
89.     SELECT CASE id
90.     END SELECT
91. END SUB
92.  
93. SUB __UI_MouseDown (id AS LONG)
94.     SELECT CASE id
95.         CASE ClickMEform
96.  
97.     END SELECT
98. END SUB
99.  
100. SUB __UI_MouseUp (id AS LONG)
101.     SELECT CASE id
102.         CASE ClickMEform
103.  
104.     END SELECT
105. END SUB
106.  
107. SUB __UI_KeyPress (id AS LONG)
108.     'When this event is fired, __UI_KeyHit will contain the code of the key hit.
109.     'You can change it and even cancel it by making it = 0
110.     SELECT CASE id
111.     END SELECT
112. END SUB
113.  
114. SUB __UI_TextChanged (id AS LONG)
115.     SELECT CASE id
116.     END SELECT
117. END SUB
118.  
119. SUB __UI_ValueChanged (id AS LONG)
120.     SELECT CASE id
121.     END SELECT
122. END SUB
123.  
124. SUB __UI_FormResized
125.  
126. END SUB
127.  

Title: Re: Mastering InForm: Click Response for Controls and for Screen Incompatibility
Post by: FellippeHeitor on September 21, 2018, 09:56:04 am

BTW, these are automatically detected as left/right if you're using Windows.

Title: Re: Mastering InForm: Click Response for Controls and for Screen Incompatibility
Post by: Qwerkey on September 21, 2018, 10:20:48 am

Fellippe, thanks.  You're too late, I couldn't wait - have implemented an Undo Button.  Will remember mouse buttons for the future.  Richard

Text Only | Text with Attachments