Visual attributes of disabled item. plase help

I have a form where when i disabled an item, this item item became unreadable, the font has blanc shine and when changing visual attributes property, can not find how to fix it. Do you have any idea? Thank you very much for your help. Thnaks.

Thanks, i think of this but the items are mainly checkbox and radio button, i need to keep enabled to false.
But would like to know is it possible to change the default visual displaying of disabled items?
Edited by: Tabit7 on Jul 18, 2011 9:41 AM

Similar Messages

Reg: visual attribute for list item

hi frs,
i have created a listitem i have used
APP_ITEM_PROPERTY2.SET_PROPERTY('list4',VISUAL_ATTRIBUTE, 'color');
in keylistval Trigger.
when i select one particular item in the list it should have background color mentioned in the VISUAL_ATTRIBUTE 'color'.
but what is happening is when i select one particular item visual attribute is set to all items in list.
why it is so?
how can i solve this problem.
any one help pls.
Thanks
Rajesh

1- I have three list box on the form as well so whether post-text-item works over therei have no issues with this and it is working fine in my forms list box
2- and i have 3 datablock among which 2nd and thid datablock is multirecord datablock where i set current record visual attribute so what is the behaviour @ run time either current record Visual attribute override current item VA or it works fine
it is working perfectly in multi record also..you need to remember in post text trigger use the same visual attribute used for current record visual attribute

Visual attribute for current item

How can i set the visual attribute of the current item in multi block form so that when user navigate through item in a form its background colour is changed and user can easily trace where the cursor is ?

1- I have three list box on the form as well so whether post-text-item works over therei have no issues with this and it is working fine in my forms list box
2- and i have 3 datablock among which 2nd and thid datablock is multirecord datablock where i set current record visual attribute so what is the behaviour @ run time either current record Visual attribute override current item VA or it works fine
it is working perfectly in multi record also..you need to remember in post text trigger use the same visual attribute used for current record visual attribute

Partially apply a visual attribute to an item

Is there any way to partially apply a visual attribute to an item?
Currently, I do not have commas for my number formats and of course, now it is required. I am limited for space and adding the comma's will cause design layout issues. I was trying to think of another way to accomplish this -- red999,black999,red999,black999.99
Any other suggesions or work arounds?
Lesson learned ;)
TIA

Sorry if I was not clear. The colors would represent the positions that would be between the commas so the user could identify, lets say, between 1000.00 and 10000.00 or 1000000.00
I was just wondering if there was a way to do this or if others have had similiar situations and may have other suggestions for a work around without having to go back and adjust my layout.

Default appearance of disabled items

Hi, i would like to have some informations on visual attributes of disabled items :
--Is it possible to change the default appearance of disabled items?
--How oracle forms manage visual of disabled items?
--Is it possible to change background or foreground color of disabled items?
Thank you very much.
Edited by: Tabit7 on Jul 19, 2011 6:30 AM

This seems a pretty simple thing to test. For example, I created a sample form and in the When-New-Item-Instance trigger I added the following code:
:BLOCK1.ITEM1 := 'TEST';
Set_Item_Property('BLOCK1.ITEM1',BACKGROUND_COLOR,'r255g255b000'); /* YELLOW */
Set_Item_Property('BLOCK1.ITEM1',FOREGROUND_COLOR,'r255g255b255'); /* WHITE */Good so far. Background is Yellow and Forground is White. Then I disabled the item.
Set_Item_Property('BLOCK1.ITEM1',ENABLED, PROPERTY_FALSE);and the text Forground color changed to light black or dark grey. So to answer your questions:
--Is it possible to change the default appearance of disabled items?Yes - but, not all attributes of the disabled item can be modified.
--How oracle forms manage visual of disabled items?The basic appearance of the item doesn't change except for the forground color.
--Is it possible to change background or foreground color of disabled items?Background color = YES, Forground color = NO.
If there are other attributes you want to change, Font Style, etc, I suggest you try to set the property and see what happens. As it turns out, you can also change the FONT_SYTLE of a disabled item as well. ; )
Hope this helps,
Craig B-)
If someone's response is helpful or correct, please mark it accordingly.

Visual attribute for records in MULTISELECT block

Hi,
For some type of records I need to set background colour yellow.
The block has property set to QMSSO$MSEL_BLOCK.
I am using below code for each field in the block displayed:
POST_QUERY for the block:
set_item_instance_property('block.column_name',l_cur_rec, visual_attribute, 'QMS$BLACK_ON_YELLOW');
Also on when-new-record-instance I have added following code for getting the yellow colour on select:
if upper(:VANN.MESSAGE_NAME) LIKE '%PROB%'
then
qms$user_prefs.set_va_selected_record('QMS$BLACK_ON_YELLOW');
else
qms$user_prefs.set_va_selected_record('QMS$WHITE_ON_DARKBLUE');
end if;
But problem is that when we navigate from record with background Yellow to any other record displayed the visual attribute is change back to Grey (yellow colour disappears).
This functionality must work for multiselect block. Is there any headstart function/utility which can help me to resolve the problem.

1- I have three list box on the form as well so whether post-text-item works over therei have no issues with this and it is working fine in my forms list box
2- and i have 3 datablock among which 2nd and thid datablock is multirecord datablock where i set current record visual attribute so what is the behaviour @ run time either current record Visual attribute override current item VA or it works fine
it is working perfectly in multi record also..you need to remember in post text trigger use the same visual attribute used for current record visual attribute

Changing visual attribute in Enter Query mode

Hello, I want to change visual attribute of all items in the first record when the user presses button for Enter_Query. I want that the user sees that the form is in enter query mode and it "waits" for the input of criteria. My code (copied from Help and modified) in trigger WHEN_BUTTON_PRESSED:
DECLARE
cur_itm VARCHAR2(80);
cur_block VARCHAR2(80);
BEGIN
ENTER_QUERY;
cur_block := :System.Cursor_Block;
cur_itm := Get_Block_Property( cur_block, FIRST_ITEM );
WHILE ( cur_itm IS NOT NULL ) LOOP
cur_itm := cur_block||'.'||cur_itm;
Set_Item_Instance_Property( cur_itm, CURRENT_RECORD, VISUAL_ATTRIBUTE,'yellow');
cur_itm := Get_Item_Property( cur_itm, NEXTITEM );
END LOOP;
END;
where yellow is the name of my visual attribute.
The problem is that I need to press the button TWICE to color the record.
Can anybody help me with this problem?
Natasa

(Wrong forum).
The problem is that enter_query stops executing your procedure until
another action ist started by the user.
You must create a short-time timer before issuing enter_query and set
your colour scheme in the when-timer-expired-trigger.

Changing Visual Attribute in a multi record block---Urgent

How do I change the visual attribute of a mutirecord item , before it shows, e.g. showing negative items as red and positive as blue.
Thanks

You can use set_item_instance property for this purpose . This is an example from Developer help manual
** Built-in: SET_ITEM_INSTANCE_PROPERTY
** Example: Change the visual attribute of each item instance in the
** current record
DECLARE
cur_itm VARCHAR2(80);
cur_block VARCHAR2(80) := :System.Cursor_Block;
BEGIN
cur_itm := Get_Block_Property( cur_block, FIRST_ITEM );
WHILE ( cur_itm IS NOT NULL ) LOOP
cur_itm := cur_block| |'.'| |cur_itm;
Set_Item_Instance_Property( cur_itm, CURRENT_RECORD,
VISUAL_ATTRIBUTE,'My_Favorite_Named_Attribute');
cur_itm := Get_Item_Property( cur_itm, NEXTITEM );
END LOOP;
END;

Dynamic visual attributes/multi-row blocks

We're using Headstart, Des2k V6.0.3.8. If you set preference CURREC = multi record block, you get the current record visual attribute (cg$current_record) attached to all displayed items in multi-row blocks. From the Headstart object library, these items also inherit a visual attribute of qms$item_font.
At runtime, Headstart code is invoked from the block's post-query trigger - this code dynamically assigns a readonly visual attribute to all items that are insert only, or the qms$item_font va to items that are update only. (Incidentally, it seems a bit strange that no va is assigned to items that are neither insertable nor updateable).
Assigning the va in this way seems to override the current record va for these items, which looks a little strange at runtime. I would prefer to see the current record va overriding the readonly/item_font va. In a future Headstart release, it would be nice if this functionality was configurable, but in the meantime can you suggest the easiest way of making this change to the Headstart code? I think it will be necessary to specifically set the va to stnd/readonly/current record in the when-new-record-instance trigger, & reset it on the post-record trigger. Once va's are being set dynamically, the current record attribute is pretty useless in multi-row blocks.
Incidentally - we've also changed the behaviour of va's in query mode processing. We wanted the query mode va to override the current record va; qms$record.highlight_items wasn't setting the selected va unless items have a current record attribute of DEFAULT. We wanted query mode to look the same regardless how many rows are in the block; it also looked a little odd in a multi-row block with overflow items, where the overflow items were being highlighted but the rest of the block wasn't. It would be nice if this was also a configurable option.

Cheryl,
Good point! It does look a bit odd. I'll take this into consideration for HSD6i.
To customize your app, try the following.
Copy qms$event_data_block from qmsevh50.pll to your application library.
Copy procedure set_nav_items_exg_record from the qms$record package in qmslib50.pll to your application library -AND GIVE IT A NEW NAME- like set_nav_items_custom.
Change your copy of qms$event_data_block to call this new procedure in the post-query event.
Modify set_nav_items_custom as follows.
============================================
procedure set_nav_items_custom
( p_block in varchar2
, p_recno in number default current_record
is
l_rg_id recordgroup;
l_rgc1_id groupcolumn;
l_rgc2_id groupcolumn;
rg_rows number;
l_item_flag varchar2(1);
l_item_name varchar2(100);
l_first_io_item varchar2(100);
begin
qms$block.init_block_rg
( p_block,false,l_rg_id,l_rgc1_id,
l_rgc2_id, rg_rows);
if id_null(l_rg_id)
then
-- no insert-only or update only items
-- in block
return;
end if;
for j in 1..rg_rows loop
l_item_name := get_group_char_cell
(l_rgc1_id, j );
l_item_flag := get_group_char_cell
(l_rgc2_id, j );
if l_item_flag = 'I'
then
if l_first_io_item is null
then
l_first_io_item := l_item_name;
end if;
-- Item is insert-only, update not
-- allowed
-- Change background color to
-- read-only.
set_item_instance_property
( l_item_name,p_recno,navigable
, property_false);
/* customization */
if get_item_property(l_item_name
, current_record_attribute) is null
or p_recno <> :system.cursor_record
then
/* end customization */
set_item_instance_property
(l_item_name,p_recno
,visual_attribute
,qms$user_prefs.get_va_readonly_item);
/* customization */
end if;
/* end customization */
else
-- Item is update-only, insert not
-- allowed */
set_item_instance_property
(l_item_name,p_recno
,navigable,property_true);
/* customization */
if get_item_property(l_item_name
,current_record_attribute) is null
or p_recno <> :system.cursor_record
then
/* end customization */
set_item_instance_property
(l_item_name,p_recno
,visual_attribute
,qms$config.get_stnd_font);
/* customization */
end if;
/* end customization */
end if;
end loop;
-- 18-1-1999: If block only contains no
-- updatebale items, there are navigable
-- items left.
-- If this is the case make first
-- insert-only item navigable again.
if get_block_property(p_block,enterable) =
'FALSE'
then
if l_first_io_item is not null
then
set_item_instance_property
(l_first_io_item,p_recno
,navigable,property_true);
end if;
end if;
exception
when form_trigger_failure then raise;
when others then
qms$errors.unhandled_exception
('qms$block.set_mav_items_custom');
end set_nav_items_custom;
============================================
Next, as you suggested, add WHEN-NEW-RECORD-INSTANCE and POST-RECORD triggers to handle movement from one record to the next.
WHEN-NEW-RECORD-INSTANCE
============================================
procedure set_nav_items_wnri
( p_block in varchar2
, p_recno in number default current_record
is
l_rg_id recordgroup;
l_rgc1_id groupcolumn;
l_rgc2_id groupcolumn;
rg_rows number;
l_item_flag varchar2(1);
l_item_name varchar2(100);
begin
qms$block.init_block_rg
( p_block,false,l_rg_id,l_rgc1_id,
l_rgc2_id, rg_rows);
if id_null(l_rg_id)
then
-- no insert-only or update only items
-- in block
return;
end if;
for j in 1..rg_rows loop
l_item_name := get_group_char_cell
(l_rgc1_id, j );
l_item_flag := get_group_char_cell
(l_rgc2_id, j );
if l_item_flag = 'I'
then
-- Item is insert-only, update not
-- allowed
-- Change background color to
-- read-only.
if get_item_property(l_item_name
, current_record_attribute) is null
or p_recno <> :system.cursor_record
then
set_item_instance_property
(l_item_name,p_recno
,visual_attribute
,qms$user_prefs.get_va_readonly_item);
else
set_item_instance_property
(l_item_name,p_recn o
,visual_attribute
,get_item_property(l_item_name
, current_record_attribute));
end if;
else
-- Item is update-only, insert not
-- allowed */
if get_item_property(l_item_name
,current_record_attribute) is null
or p_recno <> :system.cursor_record
then
set_item_instance_property
(l_item_name,p_recno
,visual_attribute
,qms$config.get_stnd_font);
else
set_item_instance_property
(l_item_name,p_recno
,visual_attribute
,get_item_property(l_item_name
, current_record_attribute));
end if;
end if;
end loop;
exception
when form_trigger_failure then raise;
when others then
qms$errors.unhandled_exception
('qms$block.set_mav_items_wnri');
end set_nav_items_wnri;
============================================
For the POST-RECORD trigger, you will have to modify your object library since this trigger is not included by default. Add the trigger to the object library CGSO$BLOCK_MR.
Then add the POST-RECORD event to your copy of qms$event_data_block.
Finally, add a procedure for the POST-RECORD trigger.
============================================
procedure set_nav_items_pr
(p_block in varchar2
,p_recno in number default current_record
is
l_rg_id recordgroup;
l_rgc1_id groupcolumn;
l_rgc2_id groupcolumn;
rg_rows number;
l_item_flag varchar2(1);
l_item_name varchar2(100);
l_first_io_item varchar2(100);
begin
qms$block.init_block_rg
( p_block,false,l_rg_id,l_rgc1_id,
l_rgc2_id, rg_rows);
if id_null(l_rg_id)
then
-- no insert-only or update only items
-- in block
return;
end if;
for j in 1..rg_rows loop
l_item_name := get_group_char_cell
(l_rgc1_id, j );
l_item_flag := get_group_char_cell
(l_rgc2_id, j );
if l_item_flag = 'I'
then
-- Item is insert-only, update not
-- allowed
-- Change background color to
-- read-only.
if l_item_flag = 'I'
then
-- Item is insert-only, update not
-- allowed
-- Change background color to
-- read-only.
set_item_instance_property
(l_item_name,p_recno
,visual_attribute
,qms$user_prefs.get_va_readonly_item);
else
-- Item is update-only, insert not
-- allowed
set_item_instance_property
(l_item_name,p_recno
,visual_attribute
,qms$config.get_stnd_font);
end if;
end loop;
exception
when form_trigger_failure then raise;
when others then
qms$errors.unhandled_exception
('qms$block.set_mav_items_pr');
end set_nav_items_pr;
============================================
Regards,
Lauri

Display item visual attribute

Hello.
Is there a way to use set_item_instance_property on display item?
Or change font color of disabled text item?
Thanks.

Set_item_instance_property is the new built-in. Don't use the old display_item. Help says: "Maintained for backward compatibility only."
Use the new one. There are all properties in the built-in you need for changing the visual attributes.
try it
Gerd

Help: How to create a visual attribute

I'd like to create VISUAL ATTRIBUTE for prompt. Will someone help me?
Thank you.

In Forms Builder there is a node for Visual Attributes. Open this node and create one of type Prompt.
Select this VA as the Prompt VA for the item prompts.

Gettng item property - prompt visual attribute

have set the prompt visual attribute to 'ACTIVE_COL'
SET_ITEM_PROPERTY ('TEST',PROMPT_VISUAL_ATTRIBUTE, 'ACTIVE_COL')
but when I try to get the value back it return 'CUSTOM'
GET_ITEM_PROPERTY ('TEST',PROMPT_VISUAL_ATTRIBUTE)
Why???

I have overcome this problem by setting item property in form design to 'ACTIVE_COL' then change it back to 'DEFAULT'
it works fine.

How can Highlight a text item with Visual Attributes

DEAR ALL,
I have an emp_dept_date block and in that block there are item by the name of to_dates in tabular form there are many dates display when user double click on the current date or any date it show the data of that date in the next block. i want to create a (when button pressed) in my Control Block that when button press the current date color changed automatically so for that what should i wirte in when button pressed.
Thanks for your cooperation
Regards,
Kamran J. Chaudhry

the is for first item in a block
Set_Item_Instance_Property('emp_dept_date.to_date', CURRENT_RECORD, VISUAL_ATTRIBUTE,'date');
this is for second item in a block
Set_Item_Instance_Property('emp_dept_date.DAILY_ID', CURRENT_RECORD, VISUAL_ATTRIBUTE,'date');
(emp_dept_date) is block name
(to_date & daily_id) is an item name
date is an visual attribute name which we create our self to define a color we want to change for the items we want to.
these both visual attributes will solve the when we click when button pressed in that change the color of the items in the block you want to change
Message was edited by:
Kamran J. Chaudhry

How do i disable menu items in Help manu, Photoshop cs6?

How do i disable menu items in Help manu, Photoshop cs6?
I packaged Photoshop cs6 using AAMEE CS6.
I need to some menu items to disable.
can any one please tell the process of doing , or which registries or files need to edit.
Appreciate the immediate response.
thanks in advance.

Hello8
Given the fact that you speak about AAMEE, it's not clear if you search for an automated and remote way to do it on multiple machines or not.
(and therefore if this thread should be moved to the relevant forum, http://forums.adobe.com/community/download_install_setup/creative_suite_enterprise_deploym ent )
To disable menu items, simply go to Edit>Menus and click on the eyeball next to the menus you do not want.
It is then possible to save it in a workspace that by default will be located there: Documents and Settings/[user name]/Application Data/Adobe/Adobe Photoshop CS6/Adobe Photoshop CS5 Settings/Workspaces (Modified)
I'm not sure if Photoshop will start if the default workspaces are removed, as there is an option to restore them in the preferences.
Also, this is not customer support, but a forum fielded by volunteers that answer when they can, so inviting for an"immediate response" has no bearing; and might even have the opposite effect, but thanks for doing it in a polite and non too demanding way!

Visual attribute help

I have Datablock A & B...
Both display 3 columns based on the same table but different schema. Each block displays 15 records .I created a pre-select trigger with the following visual attribute
For datablock A
set_block_property('A',current_record_attribute, 'SELECTED_RECORD');
For datablock B
set_block_property('B',current_record_attribute, 'SELECTED_RECORD');
How can I set it so if user chooses datablock A. the visual attribute will appear only for that block and be disabled for datablock B. and vise versa. Is there a way to set the attribute off based on which datablock the user selects

In the post-block trigger set the current record va to default, then on when-new-block-instance set the current record va to the highlight.
(these will fire less times then the record triggers above)
--pat

Visual attributes of disabled item. plase help

Similar Messages

Maybe you are looking for