Cheat Engine

[salumor]

Hey guys, so i've got these questions on the following test-code

1.a) Why does testfunc disrupt the thread?
1.b) Do I need to put both in threads or would there be any other solution?
2.) What's the difference createThread vs. createNativeThread (couldnt find anything on it)
3.) When exactly to use synchronize
4.) synchronize(messageDialog)) does not seem to work, is it already snycr. or why? (note: yeah in this case its not in a (sub) "thread" but on other tests where this was the case it was behaving identically)

[ParkourPenguin]

1 - Don't sleep in the main thread and try to access the GUI at the same time. Weird things will happen. In fact, just never sleep in the main thread at all.
If you think you need to call the `sleep` function from the main thread, use a timer instead. Timers are asynchronous and won't block.

2 - `createNativeThread` and `createThread` are the same thing. I guess `createNativeThread` is just an old name that's kept around for backwards compatibility.

3 - Use `synchronize` when you want the main thread to run some piece of code- e.g. when accessing the GUI. IIRC `print` is an exception. Everything else- forms, address list, memory records, dialogs, timers, etc.- must be accessed only by the main thread.

4 - `synchronize` takes a function. `messageDialog` returns a value, not a function.

[Dark Byte]

synchronize can access 'upvalues' if it's a local function

e.g;

[salumor]

Thanks, that clarifies some other questions I had! (and 4. yeah how could I miss that ). Additional questions

I actually wanted at some point to call testfunc() from the thread because it shall be executed after testthread() does its thing. Then I thought about them doing things individually, just wait till it happened.

? 1.a) Do I need to make the function global? Or would there be other/better ways? (also for nt I guess)
? 1.b) Is calling from the thread the preferred solution (because I dont need to wait in testfunc()) or any downsizes/additional thoughts?
✓ 1.c) Setting a value to be able to terminate on a synchronized thread-start done (but check 1.a)?
? 1.d) I have another testfunc2() - that again needs to be run after testfunc(). Do I always have to do nested calls once I start with threads? There is waitfor() but I don't see how to use it in this case.
✓ 2.) So synchronize(print,i) is not needed? Not even recommended? Or even some downside?
✓ 2.b) @DB Will that also be true when "next version CE force kills scripts that access GUI controls from a thread"

[AylinCE]

Just to give options other than "synchronized" and "thread":

There is an example that when "no" is selected in v1, it ignores v2 and jumps to v3 or stops counting with "return".

Additionally, there is function ownership within the script without observing the order.

[salumor]

Thanks. I need thread because it should be running -not infinate but "can" run- for a longer time and the 1 Dialog I am using is actually in there. Just when testing out why/preparing question it turned the way its now.

Also I did pass on arguments (thus thread, not timer - didnt like tags), but those did go the path everything alive take finally. Still I like thread because it does match the idea whats happening more (on testthread).

But yeah, it may helps others.

[Dark Byte]

freeOnTerminate is true on new threads so you can skip those

and print/printf is safe to use in any situation