Make items visible/Invisible in ENTER_QUERY mode

[Sheldon Wang]

Hi,

I have some base table items in my form. Based on a condition in a
RadioGroup, I have to hide/show some items in ENTER_QUERY mode. To do this,
I use set_item_property like the following,

to make it visible,

set_item_property('well.well_lsd', visible, property_true);

to make it invisble,

set_item_property('well.well_lsd', visible, property_false);

However if an item was made invisible previously and then was made visible
again, I cannot access the item (say using mouse or keys) even though I set

set_item_property('well.well_lsd', enabled, property_true);
set_item_property('well.well_lsd', updateable, property_true);

All the above operations are in ENTER_QUERY mode.

Any help will be appreciated.

Sheldon Wang

[Daniel Morgan]

Sheldon Wang wrote:

Don't do it in ENTER_QUERY mode: Do it before.

Daniel Morgan

[Sheldon Wang]

Thanks very much for the help.

The reason that I need to set_item_property in ENTER_QUERY mode is that I
can only decide which items to show/hide after I put block in ENTER_QUERY
mode. Specifically, after the block is in ENTER_QUERY mode, I enter a value
in an item, and some items will be displayed and others are hidden based on
the value in the first item.

Is this possible at all?

Thanks again.

Sheldon Wang

"Daniel Morgan" <damo...@exesolutions.com> wrote in message
news:3D3ABE95...@exesolutions.com...

[spademan o---[)*]

"Sheldon Wang" <sheld...@shaw.ca> wrote in message
news:Y%L_8.13858$7p1.4...@news1.telusplanet.net...

> Thanks very much for the help.
>
> The reason that I need to set_item_property in ENTER_QUERY mode is that I
> can only decide which items to show/hide after I put block in ENTER_QUERY
> mode. Specifically, after the block is in ENTER_QUERY mode, I enter a
value
> in an item, and some items will be displayed and others are hidden based
on
> the value in the first item.
>
> Is this possible at all?
>
> Thanks again.
>
> Sheldon Wang
>

Hi,

Try setting navigable = true in the same way you are setting visible and
enabled etc.

[Keld Nielsen]

pls. see inserted ...

"Sheldon Wang" <sheld...@shaw.ca> wrote in
message

news:yOk_8.15632$8D4.4...@news2.telusplanet.net.
..

> Hi,
>
> I have some base table items in my form. Based
on a condition in a
> RadioGroup, I have to hide/show some items in
ENTER_QUERY mode. To do this,
> I use set_item_property like the following,
>
> to make it visible,
>
> set_item_property('well.well_lsd', visible,
property_true);
>
> to make it invisble,
>
> set_item_property('well.well_lsd', visible,
property_false);
>
> However if an item was made invisible previously
and then was made visible
> again, I cannot access the item (say using mouse
or keys) even though I set
>
> set_item_property('well.well_lsd', enabled,
property_true);
> set_item_property('well.well_lsd', updateable,
property_true);

,UPDATE_ALLOWED and not
'updateabl'e

and I'm sure you are aware of
restricted/unrestricted ...

[Keld Nielsen]

perhaps not the most obvious insert statement
I have made in my life.
so here again ... sorry

"Keld Nielsen" <keldn...@image.dk> wrote in
message
news:vmZ_8.33799$Yf1.1...@news010.worldonline.d
k...

,UPDATE_ALLOWED and not 'updateable' <----

[Sheldon Wang]

Hi,

Thanks. I tried setting navigable = property_true as well. But it just
didn't work.

Regards.

Sheldon

"spademan o---[)*" <steve.e...@its.lancscc.gov.uk> wrote in message
news:3d3c...@news.yourcomms.net...

[Sheldon Wang]

Thanks,

Yes I am aware of restricted/unresctricted. To do this, actaully I have
tried all related properties. But it still does not work.

First I set the property in a when-button-pressed trigger,

set_item_property('well.well_le', visible, property_false);

Then I set the following properties in another when-button-pressed trigger.

set_item_property('well.well_le', visible, property_true);
set_item_property('well.well_le', enabled, property_true);
set_item_property('well.well_le', update_allowed, property_true);
set_item_property('well.well_le', insert_allowed, property_true);
set_item_property('well.well_le', query_allowed, property_true);

Any ideas/suggestions? I think the problem is with the ENTER_QUERY mode.

Thanks again.

Sheldon

"Keld Nielsen" <keldn...@image.dk> wrote in message

news:SwZ_8.33803$Yf1.1...@news010.worldonline.dk...

[Joost Bataille]

Hello Sheldon,

I'd say you need something like a 'when_validate_item' trigger in
enter-query mode, something that 'happens' after you entered the first value
is entered. All I can think of is to trap the execute_query button:
hide/view your items and put the form in enter-query mode again. This
requires an action by the user however. Or create a timer that starts when
the forms is put in enter-query mode (not very convenient, I think)

Regards.
--
Joost Bataille
University of Amsterdam ICT centre
www.ic.uva.nl

"Sheldon Wang" <sheld...@shaw.ca> wrote in message

news:Y%L_8.13858$7p1.4...@news1.telusplanet.net...

[Stjepan Brbot]

When you hide an item using:

set_item_property('well.well_lsd', visible, property_false);

Oracle hides this item but also AUTOMATICALLY disables this item. If you
want to use previously hiddened item, you have to manually set 'visible'
attribute to true but Oracle does not automatically set back enabled
attribute to true. So, you have to enable this item manually! I think
that this is not bug but documented feature!

--

Stjepan Brbot

"Sheldon Wang" <sheld...@shaw.ca> wrote in message

news:yOk_8.15632$8D4.4...@news2.telusplanet.net...

[spademan o---[)*]

"Sheldon Wang" <sheld...@shaw.ca> wrote in message

news:lH2%8.383$YR5....@news1.telusplanet.net...

> Thanks,
>
> Yes I am aware of restricted/unresctricted. To do this, actaully I have
> tried all related properties. But it still does not work.
>
> First I set the property in a when-button-pressed trigger,
>
> set_item_property('well.well_le', visible, property_false);
>
> Then I set the following properties in another when-button-pressed
trigger.
>
> set_item_property('well.well_le', visible, property_true);
> set_item_property('well.well_le', enabled, property_true);
> set_item_property('well.well_le', update_allowed, property_true);
> set_item_property('well.well_le', insert_allowed, property_true);
> set_item_property('well.well_le', query_allowed, property_true);
>
> Any ideas/suggestions? I think the problem is with the ENTER_QUERY mode.
>
> Thanks again.
>
> Sheldon
>

Have you tried executing this code in normal (not enter-query) mode? this
should narrow down where the problem lies.
BTW is the item 'well.well_le' a bog standard text item?

Steve E.

[Sheldon Wang]

Hi Joost,

Thanks so much for your response to my question. I will try to come up with
a approach based on your suggestions.

Regards.

Sheldon Wang

"Joost Bataille" <j.r.l.m.batai...@uva.nl> wrote in message
news:ahj5on$kf1$1...@mail.ic.uva.nl...

[Surfnet]

"Sheldon Wang" <sheld...@shaw.ca> wrote in message

news:Ih309.3849$Vj3.3...@news0.telusplanet.net...

> Thanks so much
Your welcome.

> "Joost Bataille" <j.r.l.m.batai...@uva.nl> wrote in message
> news:ahj5on$kf1$1...@mail.ic.uva.nl...
> > Hello Sheldon,
> >
> > I'd say you need something like a 'when_validate_item' trigger in
> > enter-query mode, something that 'happens' after you entered the first
> value
> > is entered. All I can think of is to trap the execute_query button:
> > hide/view your items and put the form in enter-query mode again. This
> > requires an action by the user however. Or create a timer that starts
when
> > the forms is put in enter-query mode (not very convenient, I think)

There are a couple of other things that can be done when a form is in
enter-query mode. You can execute the query or cancel it. You can also move
to another item so maybe the key 'next_item' trigger can be usefull. The
'tab' key on the keyboard fires this trigger.
Good luck.