Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#4376 closed defect (fixed)

Ruler 25 custom units

Reported by: tonyforster Owned by: walter
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: Ruler Version: Unspecified
Severity: Unspecified Keywords:
Cc: Distribution/OS: Unspecified
Bug Status: Unconfirmed

Description

ruler 25 os24 xo4
1)custom ruler fails silently, at custom unit less than 8mm. I do not see any need to limit the range. If the range is limited to >7mm then there should be user feedback.

2)The custom units entry toolbar should be hidden in grid etc modes, At the moment you cannot switch off that toolbar in grid etc modes and entry of values>7 reverts to ruler mode even though the main toolbar still says grid mode

3)The level tool would be good inside ruler. Can the 2 activities be integrated?

Change History (8)

comment:1 Changed 8 years ago by tonyforster

4)
There appear to be custom ruler rounding errors, eg for 8.1mm custom ruler, the 9/10 unit is a little bigger than the others

comment:2 Changed 8 years ago by walter

Pushed patches to address comments 1, 2, and 4. Can you give a further rationale for integration with Level? It would seem a more Sugary approach is to have separate apps (no Swiss army knives in Sugar).

comment:3 Changed 8 years ago by tonyforster

Thanks for the fixes. 3 OK, I was unaware that no Swiss army knives was Sugar policy. It seemed a logical progression, ruler, area tool, protractor ...

comment:4 Changed 8 years ago by walter

There is a proposal to build a protractor tool as a separate activity as well that will use the camera to let you measure angles in the physical world.

What might be an interesting direction to go would to be to add callipers to the Ruler activity,
to measure objects placed directly on the screen.

(And if combined with the Distance activity, a ruler activity could measure objects in 3-space using the camera.) But let's open separate tickets for these?

comment:5 Changed 8 years ago by tonyforster

All interesting ideas.

BTW what behaviour now do you have for custom units: 0, <0, non numeric?

comment:6 follow-up: Changed 8 years ago by walter

  • Resolution set to fixed
  • Status changed from new to closed

BTW what behaviour now do you have for custom units: 0, <0, non numeric?

It won't accept 0 or non-numeric inputs: switches to default (inches) in those cases. I suppose an alert would be better.

Regarding negative numbers, I use abs of the value input.

comment:7 in reply to: ↑ 6 Changed 8 years ago by tonyforster

It won't accept 0 or non-numeric inputs: switches to default (inches) in those cases. I suppose an alert would be better.

Regarding negative numbers, I use abs of the value input.

I like the idea of reflecting on what 0 or -ve means so I would prefer some interesting response. A divide by zero error message is good, reflect on the problems of constructing a ruler with an infinite number of marks at zero spacing. For -ve you could for example put 0 on the screen right or use -ve markings from the left

comment:8 Changed 8 years ago by tonyforster

sorry, forgot to say, I am getting the left 2cm of the bottom ruler blanked out, was that way at v25

Note: See TracTickets for help on using tickets.