Hey guys,
I used wxExecute alot and it worked so far for me nicely.
Now I get on just some machines (not on mine) the error 299 (see attached picture) with the old school wxWidgets 2.9.2 (not sure if wxExecute changed since then).
Oddly enough the Execute works in an second attempt (Execute in a timer).
Does anyone have any insight in what is happening behind the curtains?
Should I just try to catch the error with either try/catch and/or wxLogNull?
Have a great day
Natulux
EDIT: wxLogNull supresses the message. So the only question remaining is if the error could have been prevented in the first place.