Opened 8 years ago

Last modified 3 years ago

#4309 accepted enhancement

OMEdit: Status bar: Improve display of component coordinates

Reported by: Jan Kokert Owned by: Adeel Asghar
Priority: low Milestone:
Component: OMEdit Version:
Keywords: component coordinate display Cc:

Description

Sorry to bother you with another minor-issue ticket.

I noticed that in the bottom status bar ("X: ~ | Y: ~") the X and Y values are odd and not helpful. The values where probably correct back in the days, when we did not have a snap-to-grid feature. Today it is not possible to move icons to these odd positions and consequently, rounded values should be displayed instead.

Also, one can think of displaying the origin of the component which is dragged at the moment and not the mouse position. Furthermore, a delta-display and an extent-display could be added, showing how many (integer) units are moved towards right or top and showing the width/height of the object.

A good example for an excellent status bar is paint.net http://www.getpaint.net/index.html in the shape-editing mode. Paint.net is a free improved version of MS paint.

Change History (10)

comment:1 by Adeel Asghar, 8 years ago

Milestone: Future1.12.0
Status: newaccepted

I can't install Paint.Net because of LiU's installation policy but I have asked the support team to install it for me. In the meantime can you explain what is delta-display?

Also, should we just round the co-ordinates or only display according to grid size like Dymola (e.g., if grid size is 4 Dymola will display 0, 4, 8 etc.)?

comment:2 by Jan Kokert, 8 years ago

Hi!
Paint.Net was just an example. The output will be something like this:
object: extent = (20 x 20), origin = (0 | 10); current (mouse) position = (20 | 0), [dragging object: delta = (+20 | -10)]

The [] part will appear only while dragging. Further in the TextView the values are not updated and are not useful. Displaying the line and the column would be appropriate then.

Also, should we just round the co-ordinates(1) or only display according to grid size like Dymola (e.g., if grid size is 4 Dymola will display 0, 4, 8 etc.) (2)?

I prefer option (1). Then it is possible to hover around with the mouse and investigate e.g. that a certain object is in between the main grid. Another example: One likes to investigate, where the absolute top-right coordinate of a box is.
Now we have a precision of two digits and this is not useful in my eyes.

comment:3 by Adeel Asghar, 8 years ago

The coordinates values are fixed in 8567e64/OMEdit. Line and column number information is shown when user switches to text view.

I am not sure if we should add object extent, origin and dragging information. We could do that for one object but how do we show information when multiple objects are selected or moved.

comment:4 by Jan Kokert, 8 years ago

Hi Adeel,
In the current nightly build (dev-342-g78b18d8-64bit.exe 2017-04-01 03:44) I can't see any difference. Still two fractional digits are displayed. Probably I need to wait for the next nightly build.

A comment to your remark regarding multiple objects:
I looked how this is realized in Adobe Illustrator, where you can move multiple objects (it's not possible in Paint.net). Here the resulting center point of the whole group is actually calculated. Furthermore, the total extent (surrounding rectangular) is given. When moving objects, my so called "Delta-Display" is not affected by single/multiple selection. So yes, I think it should be implemented like this, but not with highest priority, as it is just a nice enhancement.

Regarding the selection of multiple object, I have a new easy ticket (#4379) for you to fix :P

comment:5 by Adeel Asghar, 7 years ago

Milestone: 1.12.01.13.0

comment:6 by Francesco Casella, 6 years ago

Milestone: 1.13.01.14.0

Rescheduled to 1.14.0 after 1.13.0 releasee

comment:7 by Francesco Casella, 5 years ago

Milestone: 1.14.01.16.0

Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0

comment:8 by Francesco Casella, 4 years ago

Milestone: 1.16.01.17.0

Retargeted to 1.17.0 after 1.16.0 release

comment:9 by Francesco Casella, 4 years ago

Milestone: 1.17.01.18.0

Retargeted to 1.18.0 because of 1.17.0 timed release.

comment:10 by Francesco Casella, 3 years ago

Milestone: 1.18.0

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.