nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bug with setVisible on a container

Emanuel

Hello, i have a issue with the IWItem.setVisible on a container, that seems to be a bug...

My box is unix solaris 8 with TS 6.7.2 SP2 and i am using both firefox and IE6 to preview / debug the form created by the attached datacapture.cfg.

The problem is pretty sick... the setVisible works only outside basic event handlers...

Any suggestions?? i am getting mad... Smiley Wink

The issue say that "object is null" inside dc_action.js line 330, when it tries to do :
field.style.display = "none";\n

Thank you Smiley Wink

Find more posts tagged with

Comments

Adam Stoller

Hello, i have a issue with the IWItem.setVisible on a container, that seems to be a bug...

My box is unix solaris 8 with TS 6.7.2 SP2 and i am using both firefox and IE6 to preview / debug the form created by the attached datacapture.cfg.

The problem is pretty sick... the setVisible works only outside basic event handlers...

Any suggestions?? i am getting mad...

The issue say that "object is null" inside dc_action.js line 330, when it tries to do :
field.style.display = "none";\n

Thank you

First of all, you do realize that Solaris 8 is not a supported platform any more - right?

However, I don't think that has much to do with the issue at hand. From the code you posted it sounds like you're saying that:

IWDatacapture.getItem("/spalle/ANQT1").setVisible(false);

works outside all of the functions, but doesn't work when called from within the

gestisciSelettorePagina

function - is that a correct interpretation of what you posted?

I noticed you had the code commented-out in various places, written various ways:

before and after the attempt to make the container visible and carefully testing each scenario independently of the others - and if it still isn't working, post a clear, detailed, description of what you tried and what you saw as a result.

Emanuel

Hi Ghoti, first fo all: thank you for the interest and sorry for the bogus post, but i got carried away and i posted that chunk of false (I use a Red Hat 4+ Distro) and badly commented information.

I took my time and created an ad-hoc case for the issue, you can find it in the zip attacched to this post: all the details of the issue are in the comment of the included file, by the way:

If i try to set a container invisible inside an event handler i get a JavaScript error that say "field is null", this does not happen if i try to call the setVisible outside the handler.

Thank you!
Emanuel.

Emanuel

Sorry for the bump, can someone try the code with the ad-hoc case i attached in the previous post?

I am starting to think that this have something to do with my TS installation.

Thank you!

Emanuel.

Adam Stoller

I don't know if this will help much, but just yesterday I implemented a DCT which hid/exposed a container based on a radio-button onChange event -- in TS 7.0 on Windows (hence, I don't know if it helps you) - but the relevant code looked something like this:[DCT][html]

<script language="javascript" location="template-type" src="local.js"/>

Grouping

[/html]The inline scripts produce container elements that contain a bunch of other items and/or sub-containers, etc.

The FormAPI code looks like this:[local.js][php]IWEventRegistry.addFormHandler("onFormInit", init);
//...
function init() {
//...
IWEventRegistry.addItemHandler("/root/metadata/grouping", "onItemChange", grouping);
//...
}
//...
function grouping(item) {
var val = item.getOptions()[item.getValue()].value;
var left_rail = IWDatacapture.getItem("/root/left_rail_content");
if (val == "Grouped") {
left_rail.setVisible(false);
}
else {
left_rail.setVisible(true);
}
}
//...[/php]Other than a rendering bug that shows up in Firefox (the re-exposed container doesn't use the full width of the window -- reported to AIWOV) it works just fine.

Emanuel

I don't know if this will help much, but just yesterday I implemented a DCT which hid/exposed a container based on a radio-button onChange event -- in TS 7.0 on Windows (hence, I don't know if it helps you) - but the relevant code looked something like this:[DCT][html]

<script language="javascript" location="template-type" src="local.js"/>

Grouping

[/html]The inline scripts produce container elements that contain a bunch of other items and/or sub-containers, etc.

The FormAPI code looks like this:[local.js][php]IWEventRegistry.addFormHandler("onFormInit", init);
//...
function init() {
//...
IWEventRegistry.addItemHandler("/root/metadata/grouping", "onItemChange", grouping);
//...
}
//...
function grouping(item) {
var val = item.getOptions()[item.getValue()].value;
var left_rail = IWDatacapture.getItem("/root/left_rail_content");
if (val == "Grouped") {
left_rail.setVisible(false);
}
else {
left_rail.setVisible(true);
}
}
//...[/php]Other than a rendering bug that shows up in Firefox (the re-exposed container doesn't use the full width of the window -- reported to AIWOV) it works just fine.

Seems like the exact example i posted in my zip, that however crashes...

I think it's something related to the version / os...

In the next few days i'm getting a new box with a fresh environment, i am gonna check there and post a followup.

Thank you Smiley Wink

PS: in the meantime, instead of setting the containers invisble i collapsed them... not the same but meh...

Firenze

Run into similar problem that you are seeing when dealing with nested containers and trying to setReadOnly attribute or default values.

If you try expanding everything by default when loading DCR, your code may work.

If so, then the bug is confirmed. Of course, expanding everything creates a performance issue with DCTs so that is not desirable.

As a workaround, you can put a try, catch around your code and suppress the error.
Not pretty but it is a workaround.