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.

Similar Messages

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

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 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

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.

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

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;

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

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

Applying visual attribute to record dependant on value

hi guys, i have a form which when queried can show 10 records at a time. What i want to do is that if a certain date field is less than the current date then apply visual attribute group to that whole record (which makes the record red).
I assume such code would go in post query and i would need to use row id or something?
or am i approaching it the wrong way.
Thanks

Yes, you can use the Post-Query trigger for this. You don't need to worry about the rowid as Forms will already know which record is being evaluated. Your code would look something like the following:
/* Sample Post-Query trigger */
/* This sample assumes you have created a Visual Attribute called "DATE_RED" */
BEGIN
   -- Just compare DATE not DATETIME
   IF ( Trunc(:BLOCK.CERTAIN_DATE) < Trunc(SYSDATE) ) THEN
      Set_Item_Instance_Property('BLOCK.CERTAIN_DATE',CURRENT_RECORD, Visual_Attribute, 'DATE_RED');
   END IF;
END;You will notice in my code sample that I am using the TRUNC function on the dates. This function will return just the date so the compare looks at just the date. If you need to compare the date AND time, then simply drop the TRUNC function from the code sample. ;)
Hope this helps,
Craig B-)
If someone's response is helpful or correct, please mark it accordingly.

Check box item visual attributes

Hi,
I set an item visual attributes like below
background color gray15
Font weight demibold
Font style Plain
Font spacing Dense
But when executing the form this check box item does not appear clearly, it is not readable, could you suggest me some visual attributes setting to make a check box item more readable?
Thanks you very much.

I think the problem is related to enabled of set_item_property of this item when it is set to property_false, the enabled property_false does not allow the visual attributes setting to display the item more readable, do you have any idea to display the item more readable when enabled is set to property_false?
Thank you very much for your suggestions.

Ask: how to set visual attribute

Hi guys,
I have a data block named BLOCK1, in BLOCK1 there is a text item named ITEM1.
I display it in tabular form, showing 10 records.
I wanted the record where the cursor's located shown in different color.
For example if the cursor at record #1, record #1 therefore is shown in RED. If the cursor is moved to record #2 then record #2 will be shown in RED and record #1 color will revert back to normal.
I tried putting WHEN-NEW-RECORD-INSTANCE trigger at BLOCK1 with the following code:
set_item_property('BLOCK1.ITEM1', VISUAL_ATTRIBUTE, 'WHITE');
set_item_instance_property('BLOCK1.ITEM1', current_record, VISUAL_ATTRIBUTE , 'RED');
I thought set_item_property('BLOCK1.ITEM1', VISUAL_ATTRIBUTE, 'WHITE') will set all records of ITEM1 to 'WHITE', then the set_item_instance_property('BLOCK1.ITEM1', current_record, VISUAL_ATTRIBUTE , 'RED') will set the particular record where the cursor is in to 'RED'...
It doesn't work. All the records that has been set to 'RED' by set_item_instance_property will stay red, set_item_property does not revert them to white.
Any ideas?

In the property palette of your block there is "current record visual attribute".
Assign a valid visual_attribute and then when you move from one record to another it will be applied to the current record.
Hope it helps you,
Fabrizio
If this answer is helpful or correct, please mark it. Thanks.

Changing current visual attribute property for the entire application

Hi All.
I want to change the current visual attribute color of my form at the application level, reason being i don't want to generate all the forms again from scratch.
I know that we can change this using visual attributes but is there a way to change this through some form setting?(Oracle 10g)

I know that we can change this using visual attributes but is there a way to change this through some form setting?(Oracle 10g) There are two settings in the formsweb.cfg that could help, but only if all of your foreground and background color settings are set to Undefined. The settings are: lookAndFeel=Oracle and colorScheme=<Choose Scheme> where "Choose Scheme is one of the following scheme's: Teal, Titanium, Red, Khaki, Blue, BLAF, SWAN, Olive, or Purple. The default is Teal.
The fact that you are using a Visual Attribute for your Forms application color scheme tells me that you are not using the default "Undefined" color setting so changing the *colorScheme* setting will _not_ have the effect you want.
Since you are using Visual Attributes (VA) to define colors, you will need to change the colors in your VA and then recompile your forms for the changes in the VA to be inherited in your forms. Sorry, that is just the way Forms works. Recompiling all of your forms due to this type of change is not that uncommon and is fairly painless if you have a shell script or batch file that compiles all of your forms for you. There are numerous posts in the forum about how to write a script that will do this, so if you don't have a script yet you can search forum for more details.
The other option would be to build your own routine that would allow you to read an environment setting or pass the setting in the URL to select a color scheme. Then create a group of Visual Attributes used by these color schemes and apply them in each Form's Pre-Form or When-New-Form-Instance triggers. This is a lot of work, but it would give you the flexibility to change your application's color scheme without having to recompile your forms.
Having said this, it begs the question - why not just use Oracle's predefined color scheme's or use the *lookAndFeel=Generic* setting so the user's desktop color scheme is inherited by your application.
IMHO, Visual Attributes are best used to accent an application rather than define their _full_ color scheme. For example, I use VAs to highlight the current record and current item as well as highlight required items.
As for using "JDAPI" as *WoMo* suggests is a design-time tool - not a runtime tool. Using JDAPI would require you to know Java and you will still have to recompile all of your forms using this tool.
Craig...

Partially apply a visual attribute to an item

Similar Messages

Maybe you are looking for