Hm, I'm still getting the flicker after deleting all minimize/maximize
calls, also hide/show calls, BUT now only after clicking to another
tab first. Quite strange but there must be something going on
internally which causes it.
Maybe some state change calls aren't checked for actual change,
and called the underlying logic all the time. Plain guessing.
Brgds,
Viktor
On Sun, Jun 21, 2009 at 10:44 AM, Pritpal Bedi<bediprit...@hotmail.com> wrote:
>
> Hi
>
>
> Viktor Szakáts wrote:
>>
>> It looks the flicker is only present with the MLE and ListBox controls.
>> They are sometimes painted in a blind state and repainted properly
>> afterwards.
>>
>> Maybe the side effect of tab activation code?:
>> oTab1:TabActivate := {|| oTab2:minimize(), oTab3:minimize(),
>> oTab1:maximize() }
>>
>> With 10 tabs such becomes not very efficient, I wonder
>> if there is a shorter way to make this.
>>
>
> You hit the bulls eye.
>
> Actually I kept these message for Xbase++ compatibility reasons only.
> In QT we don't need it. Anyhow I have commented out ::hide() | show()
> calls in ::minimize and ::maximize methods, and all is fine now.
> You can test. Just comment out these two calls in xbptabpage.prg.
> I will commit after a while, under heavy changes.
>
> Regards
> Pritpal Bedi
> --
> View this message in context:
> http://www.nabble.com/QT-demoxbp-tp24128717p24132562.html
> Sent from the Harbour - Dev mailing list archive at Nabble.com.
>
> _______________________________________________
> Harbour mailing list
> Harbour@harbour-project.org
> http://lists.harbour-project.org/mailman/listinfo/harbour
>
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
