hi!
is there some possibility in phab to init a widget as “unrealized” or
hidden so the widget isn’t shown at application start because later i
maybe want to show it
thanks!
mirtch
hi!
is there some possibility in phab to init a widget as “unrealized” or
hidden so the widget isn’t shown at application start because later i
maybe want to show it
thanks!
mirtch
mirtch <mirtch@gmx.net> wrote:
: hi!
: is there some possibility in phab to init a widget as “unrealized” or
: hidden so the widget isn’t shown at application start because later i
: maybe want to show it
One favourite trick is to set its position to large, negative values.
That way, you can realize it but no one will see it. When you want to see
the widget, change its coordinates to positive values.
thanks, but i was looking for a more generic solution
regards,
mirtch
Steve Reid wrote:
mirtch <> mirtch@gmx.net> > wrote:
: hi!: is there some possibility in phab to init a widget as “unrealized” or
: hidden so the widget isn’t shown at application start because later i
: maybe want to show itOne favourite trick is to set its position to large, negative values.
That way, you can realize it but no one will see it. When you want to see
the widget, change its coordinates to positive values.
Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems
mirtch <mirtch@gmx.net> wrote:
thanks, but i was looking for a more generic solution
PtSetResource(widget, Pt_ARG_FLAGS, Pt_DELAY_REALIZE, Pt_DELAY_REALIZE);
regards,
mirtchSteve Reid wrote:
mirtch <> mirtch@gmx.net> > wrote:
: hi!: is there some possibility in phab to init a widget as “unrealized” or
: hidden so the widget isn’t shown at application start because later i
: maybe want to show itOne favourite trick is to set its position to large, negative values.
That way, you can realize it but no one will see it. When you want to see
the widget, change its coordinates to positive values.
Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems
Derek Leach wrote:
mirtch <> mirtch@gmx.net> > wrote:
thanks, but i was looking for a more generic solutionPtSetResource(widget, Pt_ARG_FLAGS, Pt_DELAY_REALIZE, Pt_DELAY_REALIZE);
why this flag can’t be modified/set in phab? my intention was to set this
property in design-mode
in docs there is: Pt_DELAY_REALIZE
in header: Pt_DELAY_REALIZE and Pt_DELAY_ACTIVATION for this purpose
regards,
mirtchSteve Reid wrote:
mirtch <> mirtch@gmx.net> > wrote:
: hi!: is there some possibility in phab to init a widget as “unrealized” or
: hidden so the widget isn’t shown at application start because later i
: maybe want to show itOne favourite trick is to set its position to large, negative values.
That way, you can realize it but no one will see it. When you want to see
the widget, change its coordinates to positive values.
Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems
mirtch <mirtch@gmx.net> wrote:
Derek Leach wrote:
mirtch <> mirtch@gmx.net> > wrote:
thanks, but i was looking for a more generic solutionPtSetResource(widget, Pt_ARG_FLAGS, Pt_DELAY_REALIZE, Pt_DELAY_REALIZE);
why this flag can’t be modified/set in phab? my intention was to set this
property in design-mode
No idea, oversight I guess. There is a palette file that needs
to be updated when new flags/resources are added. Wait a minute,
I do not think it would be useful in design mode, since PhAb instantiates
the widget, if the delay realize was set, you would not see the widget
in PhAb. Just a guess. In short, you could place it in a pre-realize
routine.
in docs there is: Pt_DELAY_REALIZE
in header: Pt_DELAY_REALIZE and Pt_DELAY_ACTIVATION for this purpose
I have never heard of Pt_DELAY_ACTIVATION, it could be a backwards
compatibility flags.
Regards.
regards,
mirtchSteve Reid wrote:
mirtch <> mirtch@gmx.net> > wrote:
: hi!: is there some possibility in phab to init a widget as “unrealized” or
: hidden so the widget isn’t shown at application start because later i
: maybe want to show itOne favourite trick is to set its position to large, negative values.
That way, you can realize it but no one will see it. When you want to see
the widget, change its coordinates to positive values.
Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems
Derek Leach wrote:
mirtch <> mirtch@gmx.net> > wrote:
Derek Leach wrote:mirtch <> mirtch@gmx.net> > wrote:
thanks, but i was looking for a more generic solutionPtSetResource(widget, Pt_ARG_FLAGS, Pt_DELAY_REALIZE, Pt_DELAY_REALIZE);
why this flag can’t be modified/set in phab? my intention was to set this
property in design-modeNo idea, oversight I guess. There is a palette file that needs
to be updated when new flags/resources are added. Wait a minute,
I do not think it would be useful in design mode, since PhAb instantiates
the widget, if the delay realize was set, you would not see the widget
that would be exactly what I want, so the designer is able to prepare the
initial view of app, if the delayed widget is invisible, he can access it
via module-tree and make his resource-manipulations
in PhAb. Just a guess. In short, you could place it in a pre-realize
routine.in docs there is: Pt_DELAY_REALIZE
in header: Pt_DELAY_REALIZE and Pt_DELAY_ACTIVATION for this purposeI have never heard of Pt_DELAY_ACTIVATION, it could be a backwards
compatibility flags.Regards.
regards,
mirtchSteve Reid wrote:
mirtch <> mirtch@gmx.net> > wrote:
: hi!: is there some possibility in phab to init a widget as “unrealized” or
: hidden so the widget isn’t shown at application start because later i
: maybe want to show itOne favourite trick is to set its position to large, negative values.
That way, you can realize it but no one will see it. When you want to
see
the widget, change its coordinates to positive values.
Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems