The "thing", as you call it, doesn't queue anything at all, in my real case. It does its own job, perhaps it's fired by a command button, perhaps by another timer.
>The "thing" submitting requests doesn't really care if the timer is handling another request at the moment.. it should just be able to submit the request to the queue and let the timer get to it when it can.
>
>>Thinking of it, I think this one will indeed take care of complication 2 that I mentioned. I have used this.enabled=.f. in the past, but apparently it has not become part of my 'automatic coding style'. I'll try to stick to it in the future. Perhaps they should have made it a native property of the timer class.
>>
>>The first mentioned problem might be tackled by adding the line tmrTimer.enabled=.f. to the other process(es) too. But one oo-programming principle requires that objects are independent and not necesarilly - or even better: not! - aware of each other.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
