Re: [WIN] Win32Lib tab items: programmatically select; and disable?

new topic     » goto parent     » topic index » view thread      » older message » newer message

Derek,

setText doesn't seem to work for tab text; is that the wrong way to put new
text onto a tabitem?

And setTextColor only seems to work for wPuts, which writes onto a tabItem,
but not correctly (doesn't erase existing text).

Dan

----- Original Message -----
From: "Derek Parnell" <ddparnell at bigpond.com>
To: "EUforum" <EUforum at topica.com>
Sent: Sunday, October 07, 2001 11:22 PM
Subject: RE: [WIN] Win32Lib tab items: programmatically select; and disable?


>
> Dan Moyer wrote:
> >
> > There's no pressing need for disabling a tabitem, I just made the
> > controls
> > in it invisible when they're empty;  I wanted to make it easier/quicker
> > for
> > the user to know when there wasn't anything in a tabitem which had
> > content,
> > and when there was, so they'd know at a glance whether to click on one
> > or
> > not.  Might be useful, though.
>
> Dan,
> it might be better to disable the controls rather than hide them. That
> way the user can at least see what controls might be possible later.
> Also, you might like to give a visual clue by changing the text of the
> tab item , for example place square brackets around them text when it is
> "disabled". Possibly even changing the text color to
> getSysColor(COLOR_GRAYTEXT).
> ----
> Derek.
>
> >

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu