Issue 11287 - Content of property browser should follow user action
Summary: Content of property browser should follow user action
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 644
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-07 13:04 UTC by phillg
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

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


Attachments
screenshot (164.76 KB, image/jpeg)
2003-02-07 13:09 UTC, phillg
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description phillg 2003-02-07 13:04:36 UTC
Steps to reproduce:
1.  Create or open any form
2.  Go into the Design Mode
3.  Select a field and right click selecting Form

Actual Outcome:
The form properties for the entire Form (aka Standard)for comes up rather than
the field selected (check the data tab to verify).

Seen under:
Windows 2000 OOo 1.0.2 & 643C, Reproducable every time.

Other notes:
This doesn't happen when selecting the Control option, only the Form properties.
 The only way to get out of it is select a field from within the form navigator
then all fields select as normal after that.
Comment 1 phillg 2003-02-07 13:09:54 UTC
Created attachment 4598 [details]
screenshot
Comment 2 Frank Schönheit 2003-02-07 16:44:58 UTC
Phil, this works as intended:
0a. When you select "Form", then the form properties open.
0b.- When you select "Control", the the control properties open
1. When you change the selection in the view (i.e. you select one or
more other control(s)), then the property browser updates with
1a. the form which all these controls belong to (or empty, if this
isn't applicable), if the /previously displayed/ object in the browser
was a form, too
1b. the "intersection" of the controls (means: the properties which
all controls have in common), if the /previously displayed/ object in
the browser was a control, too
2. When you select anything from the form navigator, then this is
displayed in the property browser

This is no bug, it's a feature :)
Comment 3 phillg 2003-02-12 10:20:56 UTC
Re-opened after following email below between FS and myself, changing
version to 644 & type to Enhancement:

>1.  Having opened a form or created one, go into the design mode and
>> bring up the Navigator and Form Properties Browser (FPB).
>> 2.  The FPB now shows the details for the entire Form shown (i.e
>> Data = DataSource, Content Type, Content...)
>> 3.  Now select any field from the page (not the Navigator).  The FPB
>> will not change.  You can select groups or labels or anything but the
>> FPB will not update.  The Form Navigator will show the change in the
>> field select but not in the FPB.
>>
>> To fix this:
>> Click on the background of the page.  The FPB will now read "No Control
>> Selected".  Clicking on any field now bring up its form properties in
>> the FPB.
>> Alternatively:
>> Click on any field (or label) in the Form Navigator and the FPB updates
>> immediately.
>> 
>> I think I followed what you were saying relating to the Form (as I said
>> the Control aspect works fine) but surely this is a bug if you are not
>> able to change the details in the FPB by selecting the fields
themselves
>> until you click on the background or use the Form Navigator.


Well, I still have to say it works as intended  (which doesn't mean
it's intuitive, it may deserve discussion). The idea is:
Whenever you selected a form, then any action in the view (not in the
navigator) will remember and keep this "a form is shown in the PB"
state. This perfectly fits to what you've seen.

I cannot say what was the original reasoning for this behaviour (it was
before my time , anything I can think of is not very cogent ....

(btw: you can still reach the control properties by chosing "control..."
in the context menu, can't you?)

Given that when the user clicks onto some controls (while the PB is
open), it is more likely that she wants to see the controls' properties
(and not stay with the form properties, even if the controls belong to a
new logical form), it may indeed be better to consider the current
behaviour at least "to be enhanced" .

(The only scenario where the user would lose if we change this is: If
she has at least two logical forms, and wants to set up both forms, then
she needs to use the navigator then, while currently she can work with
the controls belonging to the forms. But I suppose this scenario is
rather seldom ...)


Hmm. Perhaps you're right and a request for enhancement would make sense 
Comment 4 Frank Schönheit 2003-02-12 11:26:08 UTC
grabbing, targeting, and cc'ing user experience team
Comment 5 Frank Schönheit 2003-02-12 11:26:26 UTC
accepting
Comment 6 marc.neumann 2003-09-25 13:30:48 UTC
"According to the OpenOffice.org roadmap
(http://tools.openoffice.org/releases) this issue was retargeted to
OOo Later."
Comment 7 hans_werner67 2004-02-02 12:32:22 UTC
change subcomponent to 'none'
Comment 8 Frank Schönheit 2004-07-22 11:01:58 UTC
Changing title from
  Form properties come up for entire form rather than select field
to
  Content of property browser should follow user action
to better reflect what this is now about:
The idea is that whatever the user selects (no matter whether in the document
view, or in the form navigator) is reflected in the property browser.
In particular, if the property browser currently displays (the properties of) a
form, and the user selects an control of this form in the document view, then
the property browser is to display the control. This is the most notable change
over the old behavior.

With this, the change requested here was a (welcome :) side effect of fixing
issue 31762, so this one here is fixed, too. Thus, I target it for 2.0 (this is
where issue 31762 will arrive), and set it to FIXED.
Comment 9 Frank Schönheit 2004-11-01 12:51:34 UTC
re-opening for reassignment to QA
Comment 10 Frank Schönheit 2004-11-01 12:52:30 UTC
fs->msc: please verify in CWS eforms2
Comment 11 Frank Schönheit 2004-11-01 12:52:41 UTC
fixed in CWS eforms2
Comment 12 Frank Schönheit 2004-11-01 12:53:15 UTC
re-opening for reassignment to QA
Comment 13 Frank Schönheit 2004-11-01 12:53:21 UTC
fs->msc: please verify in CWS eforms2
Comment 14 Frank Schönheit 2004-11-01 12:53:28 UTC
fixed in CWS eforms2
Comment 15 marc.neumann 2004-11-02 08:59:25 UTC
Hi,

verified in cws eforms2

Bye Marc
Comment 16 marc.neumann 2004-11-25 08:52:51 UTC
Hi,

fixed in current developer build -> close.
The current developer build can be found at
http://download.openoffice.org/680/index.html
Feel free to reopen if this issue is not fixed in the developer build.

Bye Marc