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

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

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.

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

Query for records on a block with Query Data Source Type : Procedure

Hi All,
The veriosn of form I'm using is:
Forms [32 Bit] Version 6.0.8.23.2
I have a block based on a procedure.
But when I enetr-query and search for records specific to ceratin criteria even then the result of the Query is all records.
Is Query not allowed on a block with Query Data Source Type : Procedure.
Hope my question is clear.
Thanks in advance.
Regards
Arif

When you use a table based block, forms can construct any select with any where clause based on the given inputs. Using a procedure based block, forms cannot "know" which in or out parameter of the procedure corresponds to which item. Even if Forms could pass the value of an item to an argument automagically, the procedure would have to "do something" with the argument, and you´d have to code it.
So, any item that should be used in the where-clause must be mapped to an argument.
Perhaps it would be easier to use a table based block querying a view? For DDL, you could use an instead-of-trigger on the view.
Regards,
Gerd

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

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

About Visual Attributes

1.can we create visual attributes dynamically like record groups.
2.In forms there is any bulit in which gives the RGB format of particular color,i want to change background color at runtime.
set_canvas_property(:system.mouse_canvas,BACKGROUND_COLOR,'darkred');
how i can change the background color of canvas at runtime.
thank's in advance

Though you can not create the va at runtime, if you know the possible combinations or may be 10 visual attributes, u can create in the form and set it dynamically at run time. (set_item_property )
Having said that you can not have any Visual attribute for a canvas. You can have only property class. VA is for text items... PC can not be set at run time.
Best Regards
Rajesh Alex

Differences between Property Classes and Visual Attributes

Hi folks
Can anybody know the exact difference between a property class and a visual attribute?
I'm substantially good at Forms but doesn't know the exact difference.
Any reply will be deeply appreciated.
Cheers,
PCZ

Visual Attributes are only for the visual representation of your items, buttons, blocks, canvas, ...
Property Classes are for inheriting all objects including visual attributes.
If you create a style guide for your company, then first define the visual attributes for the look and feel. After that create property classes for all of the other objects in your application. On top of that create object groups, where you centralize your property classes and visual attributes.
If you have created such a form, then call this form reference-template. Now you inherit the object-groups to a second form and call this form "template".
If you create new forms, copy the template and rename it. Then you have in all your forms inherited visual attributes, property classes, etc. and all this stuff is in one "reference-template"
try it
Gerd

Setting Prompt Visual Attribute Group

Hi,
i'm trying to set the prompt visual attribute for a text item is the Forms Builder 6i patch 5. The only available choice is default. I'm using a named visual attribute for the text item and it's working just fine.
thanks.

Sorry about this one. I've forgot to change the visual attribute type for prompt.
thanks.

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.

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

Current Record Visual Attribute

Hallo,
In a Dev.2.1 Form I have defined a Visual attribute (VA01 - black on yellow) and then in a Data Base block I have assigned VA01 to the 'current record' property.
One item of that block is not a Data Base one. When I scroll the rows of the Base Table only this item isn't affected by the current record visual attribute, i.e. it remains "black on white".
Anyone kwnows why ?
Thanks in advance.
Dino.

The 'Current record Visual attribute' property of that block is already set to VA01. The point is that all of the items of that block iherit the attribute, except the one I said, which doesn't belong to the base table. I ask if this behaviour is normal, and how to do to have also this item to be affected by the same visual attribute !
Thanks.

How to change visual attribute of particular record

Hai,
I HAVE ONE BLOCK WHICH DISPLAY RECORDS OF ALL EMPLOYEES
MY OBJECT IS WHEN EMPNO=12 THEN RECORD VISUAL ATTRIBUTE MUST BE CHANGE LET'S SAY XXX ELSE VISUAL ATTRIBUTE DEFAULT
PLS HELP

You should use the SET_ITEM_INSTANCE_PROPERTY built-in procedure ... There is an example in the on-line help of Forms Builder..
If you need to change a particular record during query , you have to use the code in the POST-QUERY trigger of the block which displays the employee data.
Simon

Visual attribute for records in MULTISELECT block

Similar Messages

Maybe you are looking for