Re: [MSEide-MSEgui-talk] TTimer.options := [to_single] ?

2018-06-23 Thread Martin Schreiber
On Saturday 23 June 2018 21:53:38 fredvs wrote: > > setting ttimer.enabled to false in dothat_and_stoptimer() is OK. > > Hum,... > > Why not directly in ttimer.ontimer() ? > > procedure ttimer.ontimer(); > begin > if all_is_ok then dothis_and_continuetimer() > else ttimer.enabled := false; >

Re: [MSEide-MSEgui-talk] TTimer.options := [to_single] ?

2018-06-23 Thread fredvs
> setting ttimer.enabled to false in dothat_and_stoptimer() is OK. Hum,... Why not directly in ttimer.ontimer() ? procedure ttimer.ontimer(); begin if all_is_ok then dothis_and_continuetimer() else ttimer.enabled := false; end; This question because of: > don't touch ttimer.enabled

Re: [MSEide-MSEgui-talk] TTimer.options := [to_single] ?

2018-06-23 Thread Martin Schreiber
On Saturday 23 June 2018 12:14:06 fredvs wrote: > Hello Martin. > > OK, capito the use of to_single. Thanks for the light. > > > Without to_single it will be triggered repetitive after setting > > ttimer.enabled to true > > > > don't touch ttimer.enabled in ttimer.ontimer. > > OK. > > But how do

Re: [MSEide-MSEgui-talk] TTimer.options := [to_single] ?

2018-06-23 Thread fredvs
Hello Martin. OK, capito the use of to_single. Thanks for the light. > Without to_single it will be triggered repetitive after setting > ttimer.enabled to true > don't touch ttimer.enabled in ttimer.ontimer. OK. But how do you do for something like this: procedure ttimer.ontimer(); begin

Re: [MSEide-MSEgui-talk] TTimer.options := [to_single] ?

2018-06-22 Thread Martin Schreiber
On Friday 22 June 2018 21:34:01 fredvs wrote: > > I never understand why you do > > Huh, in my mind, a timer works like this: > > Interval is the time between 2 ontimer-method. > > I start the timer with mytimer.enabled := true; > > If I want only one ontimer-method then I use mytimer.enabled :=

Re: [MSEide-MSEgui-talk] TTimer.options := [to_single] ?

2018-06-22 Thread Martin Schreiber
On Friday 22 June 2018 13:16:39 fredvs wrote: > > TTimer.options := []; > on my rpi ---> problems, cannot zoom anymore + > lot of ressource used. > If the time used in ontimer is bigger than the interval time there will be 100% CPU power used and the delayed ontimer events will be called when

Re: [MSEide-MSEgui-talk] TTimer.options := [to_single] ?

2018-06-22 Thread Martin Schreiber
On Friday 22 June 2018 13:16:39 fredvs wrote: > Hello Martin. > > > But what is TTimer.options = [to_single], what is the difference if not use > that option ? > With to_single the timer will be fired once after ttimer.enabled will be set to true. Without to_single it will be triggered repetitive

[MSEide-MSEgui-talk] TTimer.options := [to_single] ?

2018-06-22 Thread fredvs
Hello Martin. I did extensive test of a project on processors i386 (32 and 64 bit) Linux/FreeBSD/Windows. OK, on all OS, perfect. But on arm rpi 32 bit, there was problems, for example zooming was not working any more. After hard investigations, I did find something that fixes all. The