locator with a 'nt right' CSS class

[Rob Kolanko]

Hello,

On a browse where I need to have the navigation buttons above the browse table, to save space on the screen, I have added ' nt-right' to the CSS for the locator. This allows the locator to float to the right of the browse buttons which free a line above the browse. The float works fine as long as the navigation buttons appear. However if user selects filter where the number of records displayed does not exceed the page size, the navigation buttons will disappear, then ' nt-right' CSS class will force the locator to appear right on top of the browse header  which looks ugly and is unfunctional.  Is there a way to have  ' nt-right' CSS class when the navigation buttons appear and to remove the class or hide the locator when the navigation buttons are hidden? Is there a property that is set when the navigation buttons appear?

I have just noticed that this problem occurs only with Firefox. In IE (even IE8) and chrome, when the browse navigation buttons are hidden with these web browsers, the locator stays put.

Thanks,
Rob

[Bruce]

Hi Rob,

yeah, it's a bit of a funny one in FF. But it seems to be solved if you set the CSS for the Table DIV on the same procedure to
' nt-left'

Cheers
Bruce

[Rob Kolanko]

Hi Bruce,
Thank-you, your advice helped to fix the text overwrite issues with locator in FF. I had to apply "nt-left" css to some other hand-coded html on the web page for FF. However the "nt-left" class additions caused the bottom navigation buttons to over write the table and top navigation buttons with the Safari browser. So I have made the addition of the  "nt-left" class occur only with FF. This works with all browsers tested (IE, FF, chrome, safari). Also, in my NetWebBrowse page, I do not have Update Buttons, so the following is not an issue for me, but in testing the solution with another application, the update buttons moved from below the browse list to the top of the list when the navigation buttons disappear.  This leads to another question, for most applications, when there is only one page of records, then the locator is not needed. Is there a method to have the locator disappear with the navigation buttons? This used to be the default action prior to NT7.11.

Thanks again for your help.
Rob

[kevin plummer]

> when there is only one page of records, then the locator is not needed

I let my users decide the number of records + my browses have select all records checkbox. I would still like them to be able to use contains locator on one page with this option.

In short, I wouldn't want this option to be automatic.

[Rob Kolanko]

when there is only one page of records, then the locator is not needed

I let my users decide the number of records + my browses have select all records checkbox. I would still like them to be able to use contains locator on one page with this option.

OK, some people want the locator even when the browse has one page. Others, like me would rather the locator does not appear.  Perhaps in a future release, we could have an option on whether the locator disappear with the navigation buttons on browses with one page.

Just a thought,
Rob

[Bruce]

can I just clarify a thought, to make sure we're all on the same page - here's what I'm thinking;

a) when using a "subset" locator (begins with, contains, search) then the locator should always be visible. Even if the data is only 10 records, and all 10 are displayed, the locator still has value in reducing that set of 10 to 1 or 2 entries.

b) when using a _positional_ locator then it can go one of two ways;
b1) suppress the positional locator on browses where all the records are visible.
b2) show the locator  (the locator will highlight the record you position to, but that's about all.)

I think Rob's point is that the behavior _for positional_ locators has changed from b1 to b2.
I think Kevin's point is that for subset locators, a) is still the best approach (and has always been done this way.)
I don't think the 2 points are therefore exclusive - indeed I suspect you both agree on both points.
(adding an option to determine b1 or b2 would seem to be appropriate.)

Am I right?

cheers
Bruce

[kevin plummer]

How hard is it to have:

1 - always show the locator
2 - hide positional locator if all records visible (show subset locators)
3 - hide all locator types if all records visible

[Bruce]

not hard.

[Rob Kolanko]

Bruce,
You aright as usual.
Having the b1 or b2 option would work for me and I think it would be easiest to build.
I like Kevin' s suggestion too, and since you said that it would not be hard to do, then I think that we are all in agreement.
Rob

[Bruce]

Setting added to Locators tab in 7.31
"Show Position Locator even if all records displayed"
default is off, ie behavior b1, which was the behavior in versions past.