Issue 21129 - Ctrl-Dragging to select blocks of text.
Summary: Ctrl-Dragging to select blocks of text.
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 1.1
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: h.ilter
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-13 18:20 UTC by lazlow69
Modified: 2003-10-15 18:05 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description lazlow69 2003-10-13 18:20:56 UTC 
Including a ctrl-drag option to select non-contiguous blocks of text is an 
excellent idea, and works pretty well... but I am working in a text document 
with tables and let's say I select 5 sections of type, and am ready to select 
my 6th section of type, I am holding down ctrl while dragging, but if the mouse 
goes over the edge of a table, the whole selection set is undone.  It is quite 
frustrating, especially when I am at the culmination of selecting all the 
elements I want to select.  Let me know if this makes any sense, I'd be glad to 
elaborate if necessary.
Comment 1 Rainer Bielefeld 2003-10-13 20:25:52 UTC 
INVALID, double report of issue 21128

Rainer
Comment 2 Rainer Bielefeld 2003-10-13 20:26:04 UTC 
.
Comment 3 lazlow69 2003-10-15 02:36:18 UTC 
Perhaps this is another bug... I tried to submit this only once, 
somehow it got double submitted.  How can I see what sort of progress 
is being made on cartain bugs or potential bugs?
Comment 4 lohmaier 2003-10-15 18:03:18 UTC 
just be a little more patient when submitting bugs :-) (i.e. don't hit
the submit-button twice) When the site is on heavy load, submitting an
issue may take a while.

As the reporter (or someone who voted or put him/herself to the
cc-field) autmatically gets an email with the comments added and a
list of changes that were applied to the issue.

An alternative way is to log in to OOo. There will be a new link
called "My issues" in the left navbar. This holds a list issues you
submitted that are not yet fixed or closed.

For end-users the most-important field probably is the
target-milestone that states the version in which the fix will be
included (and available for end-users - you'll mostly find the fix in
betas for the named version as well)
Comment 5 lohmaier 2003-10-15 18:05:12 UTC 
.. A milestone "OOo later" means that there are no ressources
available to include the fix in the next version (this may change of
course)