the flags encode the several states that you can define in the UIPainter:
initially visîble/invisible
initially enabled/disabled
border IIRC
etc
I currently do not know what 32 stands for.
maybe the button was initially disabled and never enabled?
HTH
Thomas
--
> -----Original Message-----
> From: Roberto Fonseca
> [mailto:
[hidden email]]
> Sent: Friday, June 15, 2007 3:53 PM
> To:
[hidden email]
> Subject: Looking for Explanation on #flags:
>
> Hello everyone,
>
> As we continue to migrate/test the code from VW 3.0 to VW
> 7.4, we got a problem where a button was not answering to a
> click event (the button is defined in a subcanvas which is
> inside another subcanvas in the window). Even though the
> subcanvas/button was enabled, when I clicked on it nothing
> was happening. To make things a little worse, I had some
> windows where the same subcanvas/button was working
> perfectly. After spending many hours on this, I decided to
> compare the WindowSpec protocols for the working and
> non-working windows. Then I noticed that there was a
> difference in the #flags value. This is how it was defined originally:
>
> ...
> #(#SubCanvasSpec
> #layout: #(#Rectangle 425 81 513 101 )
> #name: #searchSubCanvas
> #flags: 32
> #minorKey: #searchSpec )
> ...
>
> As soon as I changed the value to #flags: 0 the button
> started working properly. I looked online (and in the docs)
> for an explanation about the #flags variable/field but
> couldn't find any. Does anyone know how #flags work? How is
> it used? Any suggestion on why we got this problem in v7.4?
>
> Thanks,
>
>
> Roberto Fonseca
>
> Solution Center
>
> Blue Heron Consulting
>
> 90 Airpark Dr, Suite 200
>
> Rochester, NY 14624
>
> www.BlueHeron-Consulting.com
> <blocked::
http://www.blueheron-consulting.com/>
>
> Office: 800.253.3449 / 585.464.8035 x 211
>
> Fax: 800.464.9901 / 585.464.9760
>
>
>
Locked
