I tried and here it seems working fine
Only problem I saw is that Dialog_BrowseForFolder function seems not adding a trailing "\"
Maybe copy/paste problem from web page?
Capture.PNG
I will try to check what is causing that copy/paste problem, maybe a unicode char is inserted like end of line or end of paragraph
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
Yes, I executed in debug step by step with F8
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
Then I don't know what's wrong.
I'll try to find out this w-e.
Edit : when I comment out this part of code, the debugger finds and error lower, again commenting out the lower error leads me deeper in the code...and so on. Seems thinDebug doesn't locate accurately what is bothering it. It will take longer to find the incriminated line.
Last edited by DirectuX; 28-03-2020 at 13:17.
ThinBasic 1.11.6.0 ALPHA - Windows 8.1 x64
Commenting out this line removes the error. Eros, did you change something to the buttons ?'Modeless CONTROL ADD BUTTON , hDlg, %button1,"Start COPY", 65, 420, 45, 20
ThinBasic 1.11.6.0 ALPHA - Windows 8.1 x64
No, didn't change anything in that area.
I'm working mostly in thinAir
Can you send me a complete code example giving error so I can test it?
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
Conversation continued in the asynchronous-file-operations thread.
ThinBasic 1.11.6.0 ALPHA - Windows 8.1 x64
Debugging a script that use an user interface message pump can create false runtime errors.
Problem is related to the fact that windows message pump is too intense to be trapped correctly so parsing of script at runtime can jump into script position different from the one expected by thinBasic Core Engine.
Windows events are fired asynchronously and stopping them at runtime by the debugger move parsing position in a place that Core do not expect.
I do not know if I will be able to solve this for the moment with current thinBasic Core structure that is single thread parsing.
The only way I see to solve this situation it to have different parsing threads working at the same time: one for Core engine and others for windows/controls events each working separately with a script pointer different for each one.
Will think about that.
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
Yes all.
And error can or cannot occurs randomly depending on messages sent to/from the script.
Maybe I will find a way to solve without recoding thinBasic from the ground up removing some events only when script is under debugging.
It would be similar to Visual Designers that remove events when in visual editing.
Will see.
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