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

Map composer glitches #437

Closed
6 of 12 tasks
thomaspiller opened this issue May 17, 2019 · 5 comments
Closed
6 of 12 tasks

Map composer glitches #437

thomaspiller opened this issue May 17, 2019 · 5 comments

Comments

@thomaspiller
Copy link
Collaborator

thomaspiller commented May 17, 2019

  • when switching from px or mm to in, the dimensions of the page change because the values are rounded to zero decimal.
  • no line breaks/word breaks in text boxes when words are very long.
  • clicking on a legend item in the composer map activates the filter in the views panel.
  • when there are several styles applied to a text element (eg bold + strike), not all styles are exported in the output.
  • text overflowing in legend boxes aligns to the left when the box is resized, while it aligns to the right while it is being typed.
  • default page size should be 600 x 600 px.
  • add vertical scroll bars in the sidebars of the map composer module.
  • the option Resolution (dpi) should not be displayed when the tool is opened because the option Unit is initially set to "px".

Firefox specific issues

  • legend is not editable, items are only removable. Text can only be added where not already present.
  • map resolution is poorer than in Chrome.
  • legends' symbols disappear as legend classes are marked-up.

Chrome specific issue

  • at high resolutions (> 400 dpi; seems to vary depending on the resolution of the screen): the map zoom is increased in both "layout" and "print" modes. At export, the map is smaller than expected because the change of zoom level is not conserved. dpi max value is set at 300. This should no longer be an issue. See Map composer: high resolution deformations #487
@davidedwardjensen
Copy link

In addition, the hover text for the map composer button is called btn_map_composer. A small issue but would be good if the naming could be consistent with the other buttons. The same comments also applies to the hover label of the btn_draw_mode button.

@antobenve
Copy link
Collaborator

antobenve commented Jun 3, 2019

Thanks @davidedwardjensen,
@thomaspiller can you please add the two items reported by David to the list of items in #327?
Can you also add to the list of map composer related glitches the following one please?

  • Please add vertical scroll bars in the sidebars of the map composer module.

@antobenve
Copy link
Collaborator

Hi @fxi, please give high priority to this development, as previously agreed:

  • Add vertical scroll bars in the sidebars of the map composer module.

Thanks

@antobenve
Copy link
Collaborator

Based on the new developments (Version 1.9.44-beta.5), a glitch is added to the list.

@thomaspiller
Copy link
Collaborator Author

I am closing this issue as most of the points have been corrected over the years and the map composer has evolved a lot recently. If improvements are still to be made, a new issue should be opened.

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

3 participants