Issue 16779 - navigation toolbar vanishes in forms
Summary: navigation toolbar vanishes in forms
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC
Hardware: PC Windows 2000
: P4 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: oooqa
Depends on:
Reported: 2003-07-13 11:36 UTC by ingenstans
Modified: 2017-05-20 10:48 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description ingenstans 2003-07-13 11:36:48 UTC
This is an issue in form design. I think it belongs in the database project. 
Even if it doesn't, I know it will get promptly dealt with here :-)

The problem is that the "Form Toolbar", as the help call it, disppears forever 
if you press the close button on one corner. It ought to reappear if you set 
"Navigaiton Bar" to yes in the "Form Properties" dialog. It does not. Though I 
have only seen this on Windows, it was confirmed, on IRC, by someone using 


Start a new form, and connect it to a database.
By default, a floating "Form toolbar" appears.
Click the close box in the top right-hand corner.
The box diappears.

Now try to restore the toolbar: open the form properties tab, and set the 
Navigation Bar to "Yes", 
Expected behaviour: the form toolbar reappears.
Actual behaviour: the form toolbar stays invisible. Nor does it appear in any 
future forms you create or open.

What is really strange is that this behaviour seems independent of particular 
forms used. In fact, with me, it persisted across an upgrade. I found the bug in 
1.1 beta 2. Even after I uninstalled that and swithced to RC1, I still don't get 
the form toolbar when I make a new form.
Comment 1 Frank Schönheit 2003-07-15 09:52:53 UTC
Problem is the "overlay" of two concepts here: The "Navigation Bar" in
the properties of a form only indicates if the bar should be visible
in general.
Additionally, the "Navigation Bar" in the context menu of an arbitrary
toolbar switches on a "navigation bar", which, depending on the
context, can be one of different toolbars. In a form, it denotes the
"form navigation bar", which in the help is called "form toolbar".

If you chose this "Navigation Bar" entry after you closed the floaring
via the "x", then it re-appears.

I submitted a new issue which requests to make the terminology
consistent, unfortunately it's in the internal bug tracking system,
because OOo at the moment does not yet know "Help" issues (AFAIK).

Additionally, I keep this issue to see if we can enforce the
visibility of the navigation bar when a form enters "alive mode".
However, this may contradict the concept of OOo's framework (the
"second layer" in the description above), but I heard that this is
going to be changed anyway :).
Comment 2 ingenstans 2003-07-15 11:22:54 UTC
Frank, thanks for your prompt attention. But which "arbitrary toolbar" 
are you referring to? I don't get a context menu offering me any sort 
of navigation toobar when I right click on the toolbars I already 
have. This is in RC1 on Windows. 
Comment 3 Frank Schönheit 2003-07-15 11:36:32 UTC
huh? The object bar, the function bar, and the main-toolbar don't have
a context menu? Or does this context menu not contain the "Navigation
Bar" entry? If the latter, then you first need to open a form.
It works perfectly here for me in 1.1 Beta 2, I do not yet have a RC1.
Comment 4 ingenstans 2003-07-15 13:34:26 UTC
OK. Got it. It only appears when the form is live. That definitely 
belongs in the help file: you're right. Thanks for your help. I would 
never in a million years have found it on my own.

I'm also putting the oooqa keyword on it, even if it's my own, just 
for housekeeping.
Comment 5 Frank Schönheit 2003-07-15 13:44:09 UTC
Well, as said, the toolbar handling is probably to be changed for OOo
2.0, but I don't know details. Let's see the plans, and then see where
this one here fits in.
The most important thing is that we get consistent terminology in UI
and help, and this is what the other bug I mentioned is about.
Thanks for your engagement :)
Comment 6 marc.neumann 2003-07-28 10:04:23 UTC
Comment 7 marc.neumann 2003-09-25 13:27:02 UTC
"According to the roadmap
( this issue was retargeted to
OOo Later."
Comment 8 Frank Schönheit 2003-10-13 09:48:03 UTC
Comment 9 hans_werner67 2004-02-02 12:15:30 UTC
change subcomponent to 'none'
Comment 10 mortmercoleth 2010-11-11 03:18:12 UTC
Created attachment 74116
Comment 11 Marcus 2017-05-20 10:48:17 UTC
Reset assigne to the default "".