Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Useability issues with scalebar component in composer #15166

Closed
qgib opened this issue May 14, 2012 · 1 comment
Closed

Useability issues with scalebar component in composer #15166

qgib opened this issue May 14, 2012 · 1 comment

Comments

@qgib
Copy link
Contributor

qgib commented May 14, 2012

Author Name: Jonathan Moules (Jonathan Moules)
Original Redmine Issue: 5589


I consider this a bug but typically most people consider this sort of thing a "feature request".

Simply put, the current scalebar thing in composer is incredibly user UNfriendly. It took me several minutes to figure out how I was supposed to get it to show units of 10km's because the map units are 1m. It seems a feat of mental gymnastics is required when setting it up, you need to change "map units per bar unit" and "segment size" to multiply together. Yes this is "easy" maths, but its also something the computer should be able to do itself.

Resizing the thing is also a nightmare.

The ArcGIS method is infinitely easier.

As such my suggestions are:

a) Allow the user to specify the units they want it displayed in. QGIS then displays the appropriate units.
b) Allow the user to resize the scale bar simply by dragging the bounding-box. This should resize units, resize bar size etc etc.

@qgib
Copy link
Contributor Author

qgib commented May 14, 2012

Author Name: Giovanni Manghi (@gioman)


same thing as #15168

It is probably (surely) possible to make things better about the scalebar, but it is a documented feature anyway.

As the request involves changing something that is (anyway) working and is documented, the right way to follow is to discuss the proposal in the users mailing list. Cheers!


  • resolution was changed from to invalid
  • status_id was changed from Open to Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant