10-06-2016, 11:39 AM
last one (for the moment)
Is a function created at QM launch and constantly monitoring an network interface for some properties is "heavy" for the system,
or is it better to have a toolbar with a procedure attached more efficient??? and for the latter, what is the message to wait for (something like WM_ADAPTERSTATUSCHANGED)?
Because I already have one toolbar used for monitoring some windows events already running...but don't want to overload it...
Is a function created at QM launch and constantly monitoring an network interface for some properties is "heavy" for the system,
or is it better to have a toolbar with a procedure attached more efficient??? and for the latter, what is the message to wait for (something like WM_ADAPTERSTATUSCHANGED)?
Because I already have one toolbar used for monitoring some windows events already running...but don't want to overload it...