[Bug 160938] FORMCONTROLS: Add ability to Find and Replace field names

2024-05-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160938

Heiko Tietze  changed:

   What|Removed |Added

   Priority|medium  |low
   Keywords|needsUXEval |
 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
   |.freedesktop.org|tion.org
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #9 from Heiko Tietze  ---
We discussed the topic in the design meeting.

Object names are unique and F is very unlikely to support some workflow. But
being an ODF editor we should have a place to find all objects, and together
with regular expressions it the function might become handy.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 160938] FORMCONTROLS: Add ability to Find and Replace field names

2024-05-22 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160938

--- Comment #8 from Steve  ---
(In reply to Heiko Tietze from comment #6)
> But anyway, the claim was made that...
> 
> (In reply to Steve from comment #0)
> > ...copying a table full of form controls is easy (copy/paste) 
> > however each field control must then be edited individually...
> Which is not true.

But it IS true! I create a lot of forms, and copied controls are not renamed. I
just updated to LO v24.2.3.2 (on Win10 x64) to verify the behaviour has not
changed.

Please see the example ODT I just uploaded. I selected the table under 1.1,
CTRL-C, moved the cursor under 1.2, CTRL-V.

Note the field names in the tables are identical. The pasted fields were not
renamed.

Furthermore, even if copied fields WERE renamed (e.g. your example of
"top_left" becomes "top_left 1"), this still would not meet my need. I need the
ability to control the field names in the copied table according to my naming
convention, rather than accepting an automated decision. The reason for this is
all around tab order usability as outlined in another feature request, bug
160918. It becomes even more critical when javascript authomation comes into
the picture.

It should not be a surprise that disciplined authors of complex forms need a
naming convention for their fields, and an easy way of adhering to it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 160938] FORMCONTROLS: Add ability to Find and Replace field names

2024-05-22 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160938

--- Comment #7 from Steve  ---
Created attachment 194288
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194288=edit
Example copy of table with form controls

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 160938] FORMCONTROLS: Add ability to Find and Replace field names

2024-05-22 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160938

--- Comment #6 from Heiko Tietze  ---
(In reply to Eyal Rozenberg from comment #5)
> How would you know...
If you select a control the respective element is selected in the Navigator,
and vice versa.

But anyway, the claim was made that...

(In reply to Steve from comment #0)
> ...copying a table full of form controls is easy (copy/paste) 
> however each field control must then be edited individually...
Which is not true.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 160938] FORMCONTROLS: Add ability to Find and Replace field names

2024-05-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160938

--- Comment #5 from Eyal Rozenberg  ---
(In reply to Heiko Tietze from comment #4)
> If you copy/paste a table with form controls the resulting names are amended
> with a number like "top_left" becomes "top_left 1". What's wrong with it?

How would you know which form has top_left and which has top_left_1, just by
looking at the field names?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 160938] FORMCONTROLS: Add ability to Find and Replace field names

2024-05-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160938

--- Comment #4 from Heiko Tietze  ---
Created attachment 194124
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194124=edit
Example document

If you copy/paste a table with form controls the resulting names are amended
with a number like "top_left" becomes "top_left 1". What's wrong with it?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 160938] FORMCONTROLS: Add ability to Find and Replace field names

2024-05-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160938

--- Comment #3 from Steve  ---
(In reply to Heiko Tietze from comment #2)
> Another F (with replace being disabled) sounds good. But isn't the sidebar
> enough to find a particular field name?

Replace is a critical part of this request. Use case detailed above.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 160938] FORMCONTROLS: Add ability to Find and Replace field names

2024-05-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160938

--- Comment #2 from Heiko Tietze  ---
Another F (with replace being disabled) sounds good. But isn't the sidebar
enough to find a particular field name?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 160938] FORMCONTROLS: Add ability to Find and Replace field names

2024-05-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160938

Eyal Rozenberg  changed:

   What|Removed |Added

 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org
   Keywords||needsUXEval
 Blocks||107742

--- Comment #1 from Eyal Rozenberg  ---
Support this.

UI-wise, it could be as easy as adding another checkbox in the F dialog: 

[ ] Field Names

like we have

[ ] Comments


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107742
[Bug 107742] [META] Form control bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.