Basic button placement question

[blunsford]

Can script buttons be placed on the vertical "status area" tool bar on the left hand side of the display?

I just need some buttons to always be available no matter what page of my 10 page report I'm on. These buttons are for quick navigation to other areas of my report so any method that would do this is appreciated.

[LiveOak]

Well, sort of.You can't actually place buttons in the status bar, it is outside of the area of a layout you can modify. You can turn off the real status bar and recreate it on the layout (take a screen shot), using buttons and scripts to emulate its functions.

I really don't like using the status bar (or a copy of it) as it make the file somewhat less than "custom". Why not turn off the status bar and create your own paradigm for navigation with a customized layout design. This capability is really what really separates the better solutions.

-bd

[CobaltSky]

Hello blunsford,

If you're talking about navigating back and forth through a report in preview mode, you might be interested to visit the following link:

http://www.nightwing.com.au/FileMaker/demos1.html#d2

From that location, you can download a demo file which shows a floating navigation pallete which is invoked in preview mode, and which provides a custom interface which replaces the functions of the Status Area.

With an approach of this kind, you can easily include other buttons that take users directly to other areas of your solution - etc.

[blunsford]

Thanks, that does answer my question.

The problem I'm trying to solve is in browse mode. I'm just trying to find a way to have a single navigation bar always visible no matter what page I'm on. The "floating palette" mentioned above would work if it were available in browse mode.

The reason it's important to do this is this application is running on a tablet PC with no keyboard or mouse attached.

Thanks again for the help.

[CobaltSky]

Hi,

There is nothing about the pallette technique that precludes it operating in other modes - it's just that the demo shows it operating in preview mode (which is because that is most often required, since all buttons except those on the status area are generally diabled in preview mode).

Essentially you need to provide scripts for all user actions, then place them on the pallette and lock it in front. The users are then unable to access anything on the main layout directly, but must work through the controls you provide on the floating pallette.

[blunsford]

Thank you. I'll look into that some more.