Re: Forms 4.0 Question : Is is possible to make a non-navigable text item not appear GRAYED?

It sure would be nice if display items didn't disappear in query mode. Does anyone know how to do this? I would like to use them as set propertiable(?) boilerplate text instead of doing smoke and mirrors with canvas views.

In article <SMUENCH.95Mar30235802_at_doh.oracle.com>, smuench_at_oracle.com (Steven P. Muench) writes:
|> %> Is it possible to make a text item non-enabled and yet make it not
|> %> grey? That is, is is possible to make a text item non-navigable, and
|> %> non-mouse-navigable and yet display it in bold (i.e. not grayed). I
|> %> want the text item to display text in bold but to be non-navigable and
|> %> non-mouse navigable. I have tried defining a visual attribute to be
|> %> bold i.e.
|> %>
|> %> SET_ITEM_PROPERTY(text_item,VISUAL_ATTRIBUTE,'bold_text_visual_attribute');
|> %>
|> %> but this appears not to work. I basically want to bold/grey a text item
|> %> programatically while making sure it is non-navigable.
|> %>
|> %> Can anyone help?
|>
|> If an item is disabled, the GUI you're running on renders it
|> accordingly. This is typically a dimmed (or grey) font to indicate
|> that the item is "not relevant here".
|>
|> If you want an item which the mouse-wielding end user cannot
|> absolutely interact with in any way, you should probably change your
|> item type from "Text Item" to "Display Item" instead. The Display Item
|> is a view-only, lightweight type of item which can take on any visual
|> attribute that a normal item can. You can make the display item
|> bevelled in or out or not at all. The point is, you don't have to
|> disable the display item to stop the mouse from clicking there.
|>
|> If you use a normal text item, then the only way to prevent the mouse
|> from clicking there is to make it disabled. You can use the item
|> properties named INSERT_ALLOWED and UPDATE_ALLOWED to control whether
|> the user can actually change the contents of the text item in a new
|> record or queried record, respectively -- independent of the item's
|> being enabled.
|>
|> The Navigable property only governs whether a keyboard or programmatic
|> navigation will enter that field or not as part of default navigation
|> sequence. The mouse user can always click into the field unless it's
|> disabled.
|>
|> Hope this helps.
|> --
|> .,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,
|> Steve Muench Email: smuench_at_oracle.com Loc: 400 OP, 1288
|> Sr. Product Manager Phone: 415 506 7000 MS: 659412
|> Enterprise/Object Fax: 415 506 7228 CIS: 73404,676
|> Tools Development
|> .,.,.,.,.,.,.,.,.,.,,.,.,.,., Oracle Corporation .,.,.,.,.,.,.,.,.,.,.,.,.,.,.,
  Received on Sat Apr 01 1995 - 00:00:00 CEST