I can confirm this behaviour.
try this make a new GUI from the template, save it then go into the debugger and set a break point in the button callback procedure and you should see an error message saying
[code=ini]Error code 4
Equals Sign Expected
line 35
CASE %WM_COMMAND[/code]
It also seems to open the debug window with random settings.
I am using the latest beta (i think)
Home Desktop : Windows 7 - Intel Pentium (D) - 3.0 Ghz - 2GB - Geforce 6800GS
Home Laptop : WinXP Pro SP3 - Intel Centrino Duo - 1.73 Ghz - 2 GB - Intel GMA 950
Home Laptop : Windows 10 - Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 2401 Mhz, 2 Core(s), 4 Logical Processor(s) - 4 GB - Intel HD 4400
Work Desktop : Windows 10 - Intel I7 - 4 Ghz - 8GB - Quadro Fx 370
I can confirm this behaviour.
Learn 3D graphics with ThinBASIC, learn TBGL!
Windows 10 64bit - Intel Core i5-3350P @ 3.1GHz - 16 GB RAM - NVIDIA GeForce GTX 1050 Ti 4GB
I don't even wanna mention it, but during my development with astroCrusher, it crashed with too.
Debugging UI application is quite complex due to the many messages are fired to the callback functions even if debugger is in "waiting for user input" mode.
In any case it dosn't have to generate errors. I will check asap.
Eros
www.thinbasic.com | www.thinbasic.com/community/ | help.thinbasic.com
Windows 10 Pro for Workstations 64bit - 32 GB - Intel(R) Xeon(R) W-10855M CPU @ 2.80GHz - NVIDIA Quadro RTX 3000
Bookmarks