Issue 8243 - Selecting one field from a group in form navigator goes into rename mode rather than single select
Summary: Selecting one field from a group in form navigator goes into rename mode rath...
Status: CLOSED FIXED
Alias: None
Product: ui
Classification: Code
Component: ui (show other issues)
Version: OOo 1.0.2
Hardware: PC Windows 2000
: P4 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: michael.ruess
QA Contact: issues@ui
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-10-11 12:10 UTC by phillg
Modified: 2003-02-22 13:37 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description phillg 2002-10-11 12:10:05 UTC
When using forms in general (under design mode) single clicking on to the
navigator list from anywhere else always selects the item for one second and
then jumps into the rename function.  [A good way to test this is keeping a
control or form properties box open then selecting an item.  Within a second the
properties box goes completely grey as it jumps to rename]  If you click on
another item directly after that it does not jump into rename, it only happens
when going to Navigator from somewhere else.
Comment 1 phillg 2002-10-11 12:19:48 UTC
Still an issue in 643 (as well as 1.0.x)
Comment 2 phillg 2003-01-26 14:12:47 UTC
Reproducable:  Every time

Steps to reproduce:
1.  Create a form then go into design mode and bring up the form navigator
2.  Select an item from the page (and its label will get selected
automatically as it is grouped together)
3.  In the FN select on of the two highlighted fields

Outcome:
The field you select goes into rename mode having briefly selected
highlighted itself only.

Expected outcome:
The field is higlighted by itself and is not in rename mode

Comment 3 phillg 2003-01-26 14:14:24 UTC
Confirming, changing component and version.
Dropping Priority and re-assigning.
Comment 4 phillg 2003-01-26 14:16:48 UTC
Amending Summary
Comment 5 Frank Schönheit 2003-01-27 08:44:08 UTC
grabbing
Comment 6 Frank Schönheit 2003-01-27 08:54:49 UTC
> Expected outcome:
> The field is higlighted by itself and is not in rename mode

why? :)
Sorry, have to ask this. In general, the in-place renaming is not a
bug, but a feature. It's triggered everytime you click onto an already
selected entry, and leave the mouse untouched for a second or so. This
is exactly what happens here (and, btw, in all other places where such
a tree control is used and allows in-place editing in general) - the
only _maybe_ strange thing, which perhaps causes your confusion, is
that the mouse click changes the selection.

Perhaps the trigger for the renaming should be changed from "click a
selected entry and leave the mouse for a second" to "click the one and
only selected entry and leave the mouse for a second".

In any way, I change the priority. We have 1-5, and I think this here
is below 3 ...
Comment 7 marc.neumann 2003-01-27 11:27:22 UTC
set to target OOo 2.0
Comment 8 phillg 2003-01-27 14:37:52 UTC
Frank,

Here's my rational for the issue.  When you auto-create a form the
label is grouped with the field.  When you have the navigator open you
it is often ideal to select one field from a group (and although you
can ctrl+click with over lapping fields it is quite difficult).  I
agree with your solution that the trigger should be changed - it's
what I expected it to be anyway...

P h i l l
Comment 9 Frank Schönheit 2003-01-27 15:55:17 UTC
> I agree with your solution that the trigger should be changed - it's
> what I expected it to be anyway...

I admit I had to explicitly try to see what the trigger actually is
:), and admittedly it's a little bit weird at the moment.

FS->GT: please care for this in the SvTreeListBox. I suggest starting
in SvImpLBox::MouseButtonDown, and setting the F_START_EDITTIMER flag
only if the which was just clicked upon is the _only_ selected entry.
Comment 10 Frank Schönheit 2003-01-27 15:57:25 UTC
changing component/QA contact to UI - this is a problem of the
respective control in general, and needs to be fixed there.
Comment 11 gunnar.timm 2003-01-29 13:00:16 UTC
write this because I have to...
Comment 12 gunnar.timm 2003-01-30 15:47:33 UTC
GT->QA: fix is in CWS OS5
Comment 13 gunnar.timm 2003-02-11 13:27:46 UTC
-
Comment 14 gunnar.timm 2003-02-11 13:28:36 UTC
-
Comment 15 michael.ruess 2003-02-11 13:48:29 UTC
Looks fixed with internal workspace. Fix will be included in
OpenOffice 1.1 Beta.
Comment 16 michael.ruess 2003-02-22 13:37:26 UTC
Checked integration with internal Milestone srx644m4s3