Hiding status bar

[David Holmberg]

Hello, there is a thing troubling me....

Is it possible to hide the status bar in a runtime solution?

[ricardito]

I'd like to know if this is possible also. I've been searching and searching... Filemaker help simply says "If your layouts are designed to take up most of the available screen space, you can hide the status bar by choosing View menu > Status Bar".

Well, that's no help because I don't want to explain to every person I sell this to to go turn that off.

Anybody know of a way?

[-Queue-]

Does the Show/Hide Status Area script step not work in a runtime solution?

[ricardito]

Status Area is not the same as Status Bar, but I think I've got it working, you have to hide it before you make the runtime - I think!

[David Holmberg]

I've tried to hide it before the creation of the runtime but it's still there when I start up the solution.....

Any other suggestions?

[ricardito]

I updated to develop 7.03 and I think that made the difference because the ones I was trying 2 days ago I had the same behavior, I'd hide before runtime and it would show.

With the update I hide before runtime and it doesn't show.

[David Holmberg]

I have 7.03 and it still shows for me, maybe one of those windows-issues, I have a long list of them now....

[Lee Smith]

Have you looked at the Kiosk mode?

I personally don't like the restrictions in it for the users, but I believe it does what you want.

HTH

lee

[SteveB]

Version 7 is probably different than v6, but check Access Privileges, then Passwords (or whatever is the equivalent in v7). Available Menu commands should be 'None'. This will lock out being able to access the status area.

Steve

[David Holmberg]

Have you looked at the Kiosk mode?

I personally don't like the restrictions in it for the users, but I believe it does what you want.

HTH

lee

My interface is restricted and I used Kiosk mode in an early face of my developing.

But I don't like the looks of it and some of my users like to have the window covering only parts of the screen.

Version 7 is probably different than v6, but check Access Privileges, then Passwords (or whatever is the equivalent in v7). Available Menu commands should be 'None'. This will lock out being able to access the status area.

Steve

I had it on "minimum" earlier, took that away but can't really remember why anymore.... have to check some old notes and see if I can come up with what the problem was....

Thanks for the ideas

/David

Edited August 11, 2005 by Guest

[Ano Nimus]

The visibility of the Status Bar is changable in the registry:

HK_Current_UsersoftwareFileMaker[runtime name]7.0ToolbarsBar0visible

If you change the value of that key to 00000000 (8 times a zero) the Status Bar is invisible.

You can't expect users to go and do that, but if you use an installer to distribute your runtime (like Inno: http://www.jrsoftware.org/isinfo.php, free and easy), you can have that change that key during the installation. (Along with the the key

HK_Current_UsersoftwareFileMaker[runtime name]7.0preferencesusername, to get rid of that irritating 'Type user name' that you get when first running the runtime).

HTH

[David Holmberg]

Hello Ano!

The username dialog I get rid of but I still can't succeed to erase the status bar.... got to be doing something wrong

all the way to 7.0 it has to be right (HKEY_Current_User/Software/FileMaker/CSOF QuizMaker/7.0) because I get rid of the username but then..

Toolbars/bar0/visible

Toolbars and bar 0 is keys and visible is a registry value set to eight zeros 00000000 (type string)

have tried to change data types etc but can't get it to work. I use Astrum Installwizard....

Any idea?

Edited September 3, 2005 by Guest

[Veselko]

Hello,

I work on FileMaker Pro 8 Advanced, and have similarly problem.

These days I work on 2 applications, and want to make runtime solutions for both of them. One of them have a hidden status bar, and second don’t. That thing makes me crazy.

:

[CobaltSky]

There seems to be some recurring confusion here. It's already been mentioned, but once more for the record, the Status Bar is NOT the same thing as the Status Area.

The Status Bar is the narrow horizontal gray band which is remarkably useless and which, by default, appears along the bottom of the application window on the Windows platform. There is no equivalent on Mac OS.

The bad news is that there is, as of FileMaker 8.0v1, no native way to script the state of the Status Bar. It can only be controlled manually from the View menu.

The good news is that there are several third party utilities which will hide the Status Bar via script. These include the SecureFM plug-in from New Millennium Communications, and the WindowUtility plug-in from PracticeMaker.

[Veselko]

Do you want to say that only with plug in I can hide status BAR?

But how runtime for one application have a hidden status BAR and for another don't?

I’ve try to make these runtime solutions 15 times, and result is always the same. For one app. status BAR is hidden, and for second is not.

[CobaltSky]

Hello Veselko,

The Status Bar can be removed manually by the end-user, or can be removed automatically via the user of third-party tools such as the two plug-ins I mentioned.

The state of the Status Bar is stored in the preference settings within the registry database for each instance of FileMaker (or a FileMaker runtime) on a given computer. This is why whenever you run one runtime the Status Bar is showing and when you run the other it is not. Each has its own registry file on your computer and the settings in each of those files are preserved.

When you install either runtime on a different computer, the first time it is run it will create a new default registry entry in which the 'bit' for the state of the Status Bar will be set to its default value and the Status Bar will be shown.

[David Holmberg]

But can't you control this with Anos method?

I just thought I couldn't get it to work because I did something wrong.. It's terrible to have it there displaying the "for help press F1" when there is no help when pressing F1....

[Veselko]

I try to use Innosetup but like David said, same thing. Plus, standard toolbar is here. :

Innosetup bring possibility to change Registry and it's cool, but does not work... or I does not know how to use it properly.

[Veselko]

When you install either runtime on a different computer, the first time it is run it will create a new default registry entry in which the 'bit' for the state of the Status Bar will be set to its default value and the Status Bar will be shown.

Hi Cobalt,

Default registry entry for Status Bar is not always “to be shown”.

In one day, I create two different runtimes, and for one default registry is “shown”, and for second is “not”.

[CobaltSky]

...In one day, I create two different runtimes, and for one default registry is “shown”, and for second is “not”.

Hi Veselko,

The most likely reason for what you saw is that a runtime had previously been created/installed/used on the same machine with the same name as one of the runtimes you created and there was therefore a pre-existing registry entry for that runtime.

However that may be, you can take it from me that a fresh install of a runtime - or in fact of FileMaker Pro itself - always defaults to the Status Bar "on" state. There is no process by which a registry file can natively be generated in any other state at install. :

[Veselko]

Along with the the key

HK_Current_UsersoftwareFileMaker[runtime name]7.0preferencesusername, to get rid of that irritating 'Type user name' that you get when first running the runtime.

HTH

Works fine, but please help me how to implement your first advice. Two days I try to figure out...

Is there (on picture) must be checked one or more flags? Or something else...

TIA

Edited September 9, 2005 by Guest
Forgot to attach picture

[Wayne@Cornerstone]

You can create a script to hide status area and Tool bar and run script every time you go to that page. But not status Bar.

Edited September 10, 2005 by Guest