Issue 104774 - Ruler snap-to-grid for positioning tabs and indents not present
Summary: Ruler snap-to-grid for positioning tabs and indents not present
Status: CLOSED DUPLICATE of issue 24070
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: OOO310m9
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: writerneedsconfirm
QA Contact: issues@sw
Keywords: oooqa
Depends on:
Reported: 2009-09-04 05:26 UTC by drankinatty
Modified: 2009-09-04 13:21 UTC (History)
2 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description drankinatty 2009-09-04 05:26:11 UTC
OO Devs,

    On of the biggest problems in oo-writer is trying to place indents or tabs
on the ruler at the same location. The reason is there is no snap-to-grid or any
kind of snap to major or minor tick marks in the rule. There is no constraint at
all on horizontal positioning which leave the user trying to position tabs on a
"pixel" basis which results in tabs placement being visibly misaligned and
difficult to fix.

    For instance, if I position a tab at say, the 1/2 inch mark on one
paragraph, since there is no snap that causes the tab to position at exactly .5
inch, the tab may very well end up positioned anywhere between .47 inch to .53
inch. A few paragraphs down, the same thing occurs and the tab placement is
again guess work any where between .47-.53 because nothing helps the tab get set
at exactly 1/2 inch.

    In all other word processors the ruler has a snap feature that "helps" users
place the tab by constraining tab placement to say 1/16 inch intervals or some
major-minor grid pattern in the ruler. If the user needs or wants unconstrained
placement, then holding the shift or alt key usually disables the snap-to-grid

    This would be the most apparent fix for oo-writer in a long time. Thanks.
Comment 1 Rainer Bielefeld 2009-09-04 05:49:21 UTC
Yes, that would be useful. We already have a "Milesone 3.x" issue for that. 

May be you want to vote for Issue 24070?

*** This issue has been marked as a duplicate of 24070 ***
Comment 2 Rainer Bielefeld 2009-09-04 05:50:27 UTC
Comment 3 drankinatty 2009-09-04 13:21:50 UTC
Yes, Thank You, I will vote for it,

Will it be fixed this time? Why do I ask?

It seems this issue has been around since version "1.0" and it still isn't
fixed. So does the "Milestone 3.X" issue mean that OO is serious about
implementing the feature now??