Yesterday, 10:39 AM
Hi,
First there is an error on line755.
If = Text.IsSubText(datentb, "<H 112 1>") Then
I assume this should be without the =
Second, without your hardware and no idea how to control the program it is hard to know, but if I alter the program to just call subroutine PrüfeRückmeldungenEinfach() with <H 112 1> in textBox tb1 then the gate near the top opens, so this bit works fine.
So, all I can suggest is to add TextWindow.WriteLine debugging, or if you are using SB-Prime, then run the program in debug mode or use the Flow Chart tool to help trace the flow of the program.
Also, Scout's suggestion about performing all actions in a main 'Game loop' controlled by flags set in events is a good one in general for interactive event driven programs - it keeps all the program activity on the main UI thread (sequential) while just using event subroutines that can run asynchronously (at the same time) to set flags used within the 'Game loop'. This is not just a 'nice idea', it is how all interactive programs usally are written and keeps the program logic nicely confined, sequential, debuggable. Here is a link on this:
https://learn.microsoft.com/en-us/archiv...ent-basics
Finally, I really like the look of the program, you have put a lot of work into it.
First there is an error on line755.
If = Text.IsSubText(datentb, "<H 112 1>") Then
I assume this should be without the =
Second, without your hardware and no idea how to control the program it is hard to know, but if I alter the program to just call subroutine PrüfeRückmeldungenEinfach() with <H 112 1> in textBox tb1 then the gate near the top opens, so this bit works fine.
So, all I can suggest is to add TextWindow.WriteLine debugging, or if you are using SB-Prime, then run the program in debug mode or use the Flow Chart tool to help trace the flow of the program.
Also, Scout's suggestion about performing all actions in a main 'Game loop' controlled by flags set in events is a good one in general for interactive event driven programs - it keeps all the program activity on the main UI thread (sequential) while just using event subroutines that can run asynchronously (at the same time) to set flags used within the 'Game loop'. This is not just a 'nice idea', it is how all interactive programs usally are written and keeps the program logic nicely confined, sequential, debuggable. Here is a link on this:
https://learn.microsoft.com/en-us/archiv...ent-basics
Finally, I really like the look of the program, you have put a lot of work into it.
![[-]](https://litdev.uk/mybb/images/collapse.png)