On Thu, Jan 17, 2013 at 9:28 AM, Staffan Tylen <staffan.tylen@gmail.com> wrote:

I'm not sure where we are standing with this at the moment but I would prefer to have what you Mark call 'special treatment' of static controls in the same way as group boxes so that the code in my example can resize correctly, with or without flicker.

Where we stand right now is:  my current code treats static controls so that the code in your example resizes correctly.  But that code is not checked in yet.  For certain, you will be able have your dialogs resize static controls correctly.

The only question left in my mind, is whether to allow the Rexx programmer to change how the static control is handled.  If I don't add a method to change how the static control is handled, then your example will resize correctly.  If I do add a method, then you may need to invoke that method, depending on what the default is set at.

The bottom line is, you example will for sure be able to resize correctly.

As I pointed out earlier, resizing is nothing one is doing all the time so by remembering the current window size as the default for the next session, the programmer can make resizing an infrequent action. My question is: is this flickering problem something specific to ooRexx or does it apply to all Windows applications written in C++ and the like?

The problem is a universal Windows problem.  It has nothing to do with ooRexx, or even what language the application is written in.  Actually, the problem is just a universal problem.  All graphical user interfaces have the problem of flickering if windows are resized dynamically.  Some graphical interfaces may provide easier to use ways to reduce the noticeable flicker than others, and better hardware will also make flicker less noticeable.

Mark Miesfeld