@SW_LOCK/UNLOCK causes flicker

[Champak]

I'm using the @SW_LOCK/UNLOCK feature to basically freeze a few controls of my gui until all the data is set to print and then unlock it so updated data doesn't "scroll" while printing. The problem is it causes the whole gui to flicker/flash (basically all the controls disappear for a split second, which I find kind of annoying). Is there a workaround? Can I just lock the specific controls?

[Valuater]

GUICtrlSetState( $Control, $GUI_DISABLE)

... you should know how to use help by now Champak

8)

[Champak]

I'm sorry, I know about the disable/enable, I guess I overstated/understated my needs/issues and what I'm looking for as the outcome. I kind of still want to freeze the GUI and not individual controls because even when you freeze the controls, it still scrolls through the controls while you reenable them (so one control updates at a time). I was using the disable/enable feature before I moved onto freezing the whole gui. So let me retract the need to freeze individual controls and ask is there a way to freeze the whole window without causing the flicker.

[ResNullius]

So let me retract the need to freeze individual controls and ask is there a way to freeze the whole window without causing the flicker.

GUISetState(@SW_DISABLE) ?

[laffo16]

i still dont understand this very clearly, could somebody help me, im aware of macros just unsure how to impliment them.

if i'm going update 8-10 different labels. every 500ms, which order do i cast these in,

GUISetState(@SW_SHOW)

loop starts

GUISetState(@SW_DISABLE)

GUISetState(@SW_LOCK)

i dont see how GUICtrlSetState($Control, $GUI_DISABLE) would make any difference casting at this point?

+ i dont want to grey out the text anyway?

-update labels but check first to see if the data has changed (*)

GUISetState(@SW_UNLOCK)

GUISetState(@SW_DISABLE)

loop ends

when i use GUISetState(@SW_LOCK/UN_LOCK) the whole GUI flickers, what am i doing wrong here?

(*) i havent implemented this in my tests just yet.

perhaps i should

"try without the @SW_LOCK and @SW_UNLOCK. use ControlSetText, instead of GUICtrlSetData, Check Data is different before updating"

Edit: i made an absolute noob mistake of leaving a few extra guictrlsetdata() in where they shouldnt have been and it turns out these were the cause of the flicker, *slaps him self in the face*. in the end all i used out the above methods, was a simple check data is different before updating.

Edited April 11, 2009 by laffo16