Good afternoon, Pierpaolo Martinello,
Thank you for your feedback.
I would like to inform you that I made a mistake and reversed the screen configuration. My intention is to allocate it to the right in the internal editor, allowing you to expand any function in real-time while coding. This correction has already been made, and after testing the new version of miniGUI, I plan to push it to GIT.
As for the request to stop the process, please see the example below:
You should include DoEvents
inside the loop; this way, you will be able to abort the test. If there is an output with ?
, the test will also stop automatically when it reaches 1,000,000 prints.
Now, if you haven't included any output with ?
and also forgot to add DoEvents
, the system will only stop when the application is closed by the task executor, as there's no way to capture the cancellation without DoEvents
, unless the call was made through threads. However, that would require making too many changes, which is not worth the effort.
But I'll think of a less labor-intensive solution...
Best regards.
--
Você recebeu essa mensagem porque está inscrito no grupo "Designer Minigui Extend" dos Grupos do Google.
Para cancelar inscrição nesse grupo e parar de receber e-mails dele, envie um e-mail para designerminig...@googlegroups.com.
Para ver esta conversa, acesse https://groups.google.com/d/msgid/designerminigui/c380dba4-45d3-41b6-9873-ac3a43e42b86n%40googlegroups.com.
?
will automatically call DoEvents
. This should significantly slow down the processing, but I think this will work better. Sometimes, I also forgot to add DoEvents
in the script.