Re: SystemDependentDataBuffer bits ...

2019-04-26 Thread Jan-Marek Glogowski
So replying to myself. Am 26.04.19 um 16:46 schrieb Jan-Marek Glogowski: > Hi everyone, > > the following is just some guess work, as my build will take much longer to > verify. > > I had a look at the code and the timer fires every second. That would mean one > call to Start() for every second

Re: SystemDependentDataBuffer bits ...

2019-04-26 Thread Michael Meeks
On 26/04/2019 13:43, Thorsten Behrens wrote: > Right - IIRC that was very trivial hairlines there, not much value in > buffering that - =) >> * should we not disable the SystemDependentDataBuffer ie. >>remove: >> >> if(maEntries.empty() && maTimer) >>

Re: SystemDependentDataBuffer bits ...

2019-04-26 Thread Jan-Marek Glogowski
Hi everyone, the following is just some guess work, as my build will take much longer to verify. I had a look at the code and the timer fires every second. That would mean one call to Start() for every second, which could trigger the message via timeout, which is slightly less then: > vmiklos:

Re: SystemDependentDataBuffer bits ...

2019-04-26 Thread Thorsten Behrens
Hi Michael, let me jump in for the moment - Michael Meeks wrote: > It seems odd that just typing in writer should be so rapidly creating > and destroying these cached items. > Right - IIRC that was very trivial hairlines there, not much value in buffering that - > * should we not dis

SystemDependentDataBuffer bits ...

2019-04-26 Thread Michael Meeks
Hi Armin, I guess you missed the appended on IRC. It seems odd that just typing in writer should be so rapidly creating and destroying these cached items. A couple of thoughts: * do we need to do this for simple / common polylines etc. ? + surely there is