| View previous topic :: View next topic |
| Author |
Message |
bknight2602 Grandmaster Cheater
Reputation: 0
Joined: 08 Oct 2012 Posts: 605
|
Posted: Sat Apr 04, 2026 4:08 pm Post subject: Number of orints |
|
|
| I am executing code on a game that has nested loops and the intersections can be long, so long in fact that the print statements in the second loop quit after n records then the table exits get a little reddish along with an hourglass present. What is the number of prints prior to CE not being able to process them?
|
|
| Back to top |
|
 |
Dark Byte Site Admin
Reputation: 473
Joined: 09 May 2003 Posts: 25912 Location: The netherlands
|
Posted: Sun Apr 05, 2026 1:43 am Post subject: |
|
|
That's up to windows , message buffer, and how fast your system is.
but you can prevent the lockup by not running the code in the same thread as the GUI, or process the messages so windows won't think CE has frozen
e.g:
| Code: |
for i=1,8000 do
print(i)
processMessagesPaintOnly()
end
|
without the processMessagesPaintOnly() command CE would freeze for me at around 1800
_________________
Tools give you results. Knowledge gives you control.
Like my help? Join me on Patreon so i can keep helping |
|
| Back to top |
|
 |
bknight2602 Grandmaster Cheater
Reputation: 0
Joined: 08 Oct 2012 Posts: 605
|
Posted: Sun Apr 05, 2026 7:24 am Post subject: |
|
|
| Dark Byte wrote: | That's up to windows , message buffer, and how fast your system is.
but you can prevent the lockup by not running the code in the same thread as the GUI, or process the messages so windows won't think CE has frozen
e.g:
| Code: |
for i=1,8000 do
print(i)
processMessagesPaintOnly()
end
|
without the processMessagesPaintOnly() command CE would freeze for me at around 1800 |
Interesting. I did it another way, just commented out the print statement.
Thanks
|
|
| Back to top |
|
 |
|