Issue 53560 - Controls should stay in design mode
Summary: Controls should stay in design mode
Status: UNCONFIRMED
Alias: None
Product: Impress
Classification: Application
Component: editing (show other issues)
Version: 680m125
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2005-08-19 22:07 UTC by wgunruh
Modified: 2013-02-07 22:39 UTC (History)
2 users (show)

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


Attachments
A sample bugdoc prepared with OOo 2.0.2 (23.65 KB, application/vnd.oasis.opendocument.presentation)
2006-07-27 03:24 UTC, tora3
no flags Details
Its snapshot (3.08 KB, image/png)
2006-07-27 03:24 UTC, tora3
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description wgunruh 2005-08-19 22:07:25 UTC
If you create a new hyperlink button (Insert->Hyperlink->Form->Button) in a new
presentation the button is selectable, moveable, and erasable (it does not seem
to be editable in any way). HOwever if that Presentation is saved and then
reopened for example at a later time, That button is now unselectable,
unmoveable, unerasable.
Furthermore ALL hyperlink buttons which are created in that document now are
similarly unselectable, unmoveable, and uneraseable, which is pretty useless as
they are created in the middle of the page, where they sit forever. 

That button IS contained in Edit->Select All where it moves or shrinks with the
whole selection, but as an individual it is unselectable. This bug is in 
1.1.0, 1.1.3 and 1.1.4 (which are the only ones I have tried).
Comment 1 Regina Henschel 2005-08-20 11:44:37 UTC
Those hyperlinks are handled as controls. So you must use "Design Mode on/off".
To use it in Impress, you can customize your menu, keyboard or toolbar. You will
find this function in the category "Controls".
Comment 2 Regina Henschel 2005-08-20 11:46:34 UTC
closed as worksforme
Comment 3 wgunruh 2005-08-20 16:41:17 UTC
Then the absence of this on any menu  as delivered AND the fact that when the
document is saved and restored, that flag is changed are both bugs. 
To imagine that any user could intuit that there was a hidden flag setting which
changed and controled this behaviour is completely meshugena.

PLEASE FIX THIS BUG. It has cost me about 5 hours of my time wehn I was supposed
to be getting a talk ready for an international conference.

Note that on going through the forums, this topic has come up time and time
again with no response by anyone. It has even come up in the this bugs reporting
slightly disguised, and this solution has never been given.

For those poor souls following me, you need to right click on one of the menu
bars to bring down an menu. Under Configure... choose Menu.
Go down to the Tools section and select say the Eyedroper entry. 
Now go down and select  Category->Controls, Function->DesignMode On/Off
and click on New. YOur Tools menu will now contain a new entry.
If it is on, you can select and move the buttons. If off, you cannot. 
Comment 4 wolframgarten 2005-08-30 10:06:43 UTC
How so many things this has two sides you can look upon. when yopu design a doc
with controls it can be annoying when it always comes up in design mode off. BUT
if you have a doc you send to a friend or customer to use you do not want to
have it in design mode. Since this behaves like it is designed this is more an
wish for an enhancement than a bug.
I change the summary and reassign the issue.
Comment 5 tora3 2006-07-27 03:24:26 UTC
Created attachment 38060 [details]
A sample bugdoc prepared with OOo 2.0.2
Comment 6 tora3 2006-07-27 03:24:54 UTC
Created attachment 38061 [details]
Its snapshot
Comment 7 tora3 2006-07-27 03:33:59 UTC
Please ignore two attachments above.

I cannot believe the user interface of Issue Tracker:
 1. Making a query.
 2. Visiting one of the issues listed.
 3. Posting an article into it.
 4. Attempting to attach a file to it. But the attempt results in failure. 
    The file gets attached to another issue listed at the next position.

Anyway, sorry about that.