Ok Fred, 1. Without flushgdi := TRUE; in my program, but with -dmse_flushgdi option and with msegui sources untouched there is incredible slowness = unusable.
2. With flushgdi := TRUE; but without -dmse_flushgdi and unmodified msegui sources is a little better, as in my movie, but still flickering. 3. Modifying the sources just disable flushgdi and program is performant but smudges. I tried all these options. No luck, I think the design has problems. On Fri, Mar 19, 2021 at 7:03 PM fredvs <[email protected]> wrote: > > Actually, what you see there, is without -dmse_flushgdi > > but with the flushgdi := TRUE; inserted in my program. > > Huh, it does the same, when you add -dmse_flushgdi, at initialization of > msegraphic.pas it does flushgdi := TRUE. > > "flushgdi" is used in many units, it is why it is important to know what > "flushgdi" fixes the problem. > > If you add "flushgdi := TRUE" in your program, each unit will use it. > It is why I asked in last proposition to not set "flushgdi := TRUE" but > only > change the one in msegui.pas. > > About your last video, yes, I have just the same result as you on my i5 > compiling with "-dmse_flushgdi" or only changing in msegui.pas. > > So it is obvious that using "-dmse_flushgdi" is not the solution but can > give us some way to find where is the problem. > > > > -- > Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ > > > _______________________________________________ > mseide-msegui-talk mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk > -- Vasi
_______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
