Re: [Qgis-developer] [QGIS-UX] Print layout: canvas extent not updated

2016-06-11 Thread Nyall Dawson
On 12 Jun 2016 06:39, "Alexandre Neto" wrote: > > I like the idea of a extent toolbar, with set extent to match map canvas and the opposite. Also having bookmarks would be nice. Those buttons should only work for a selected map item, because you may have several maps in the same composer. Sorry,

Re: [Qgis-developer] [QGIS-UX] Print layout: canvas extent not updated

2016-06-11 Thread Alexandre Neto
I like the idea of a extent toolbar, with set extent to match map canvas and the opposite. Also having bookmarks would be nice. Those buttons should only work for a selected map item, because you may have several maps in the same composer. Alexandre Neto A sáb, 11/06/2016, 17:59, Régis Haubourg

Re: [Qgis-developer] Possible QGIS D3 Data Analysis Plugin

2016-06-11 Thread Matteo Ghetta
Hi, Thanks to Paolo and Rene-luc for pointing out.. Me and Michael are currently working on a plugin that plots D3 interactive plots.. In a first release (hopefully we will release soon a first version) the user will be able to draw some plot types and also have a "feedback" between the plot and

Re: [Qgis-developer] [QGIS-UX] Print layout: canvas extent not updated

2016-06-11 Thread Paolo Cavallini
Good points, thanks for comments. Perhaps a more evident button, or a notice to the user (want to update the view?) would be enough. I have an issue in distributing print layouts: in this case the first appearance will be completely off the real map, and this can be really confusing. Maybe bette

Re: [Qgis-developer] [QGIS-UX] Print layout: canvas extent not updated

2016-06-11 Thread Régis Haubourg
Agreed. What I found during training session is that the "zoom to map extent" buttons are too hard to find for most users. Even some advanced users where zooming maps with mouse scroll, not remembering those buttons from courses. Maybe some UI tweaking could help here. Why not a button in toolbar?

Re: [Qgis-developer] [QGIS-UX] Print layout: canvas extent not updated

2016-06-11 Thread Saber Razmjooei
The current behaviour is great, but having an option to use spatial bookmarks (to the best scale) within the composer will be ideal: http://hub.qgis.org/issues/12083 Cheers, Saber -Original Message- From: Qgis-developer [mailto:qgis-developer-boun...@lists.osgeo.org] On Behalf Of roy r

Re: [Qgis-developer] [QGIS-UX] Print layout: canvas extent not updated

2016-06-11 Thread roy roy
very often composer layout scale have nothing to do with canvas workflow, it should be "static" as the current behaviour, thanks, Roy Il 11/06/2016 13:52, Nathan Woodrow ha scritto: > +1 for what is currently there. One of the main reasons I move from > MapInfo to QGIS was this, annoying when

Re: [Qgis-developer] [QGIS-UX] Print layout: canvas extent not updated

2016-06-11 Thread Mathieu Pellerin
+100 to stick with current behaviour. My canvas extent very rarely reflects desired extend and scale of my composer layouts That said, for your use case, maybe you want to implement a [x] keep extend and scale synchronised with canvas. Off by default :) On 11 Jun 2016 18:52, "Nathan Woodrow" wrot

Re: [Qgis-developer] [QGIS-UX] Print layout: canvas extent not updated

2016-06-11 Thread Nathan Woodrow
+1 for what is currently there. One of the main reasons I move from MapInfo to QGIS was this, annoying when you are editing and return to print and it's moved on you. On Sat, Jun 11, 2016 at 9:44 PM, Anita Graser wrote: > On Sat, Jun 11, 2016 at 1:32 PM, Paolo Cavallini > wrote: > >> Il 2016-0

Re: [Qgis-developer] Print layout: canvas extent not updated

2016-06-11 Thread Anita Graser
On Sat, Jun 11, 2016 at 1:32 PM, Paolo Cavallini wrote: > Il 2016-06-10 19:34 DelazJ ha scritto: > >> You mean the first time the print layout is opened (created). If so, >> yes this is the way it used to work (and I think it still does): at >> the creation the map extent is picked from the canva

Re: [Qgis-developer] Print layout: canvas extent not updated

2016-06-11 Thread Paolo Cavallini
Hi, Il 2016-06-10 19:34 DelazJ ha scritto: You mean the first time the print layout is opened (created). If so, yes this is the way it used to work (and I think it still does): at the creation the map extent is picked from the canvas. But imo there's no reason to have the composer map item ext

Re: [Qgis-developer] Geocoding plugin: a good case for merge

2016-06-11 Thread Richard Duivenvoorde
On 09-06-16 12:11, Paolo Cavallini wrote: > Il 09/06/2016 12:07, Richard Duivenvoorde ha scritto: >> Should we write a QEP for this? > > +1 > Richard, would you mind writing to all geocoder developers to ask for > collaboration? I think several of them are not on this ML. QEP: first try done: ht

Re: [Qgis-developer] Geocoding plugin: a good case for merge

2016-06-11 Thread Alessandro Pasotti
2016-06-09 14:02 GMT+02:00 : > Hello, > > It could also be very interesting to have one or more Processing module(s) > for geocoding (natives QGIS "algorithms"). We could then chain this with > other algorithms (find all objects of a layer intersecting a 500m buffer > from the positions of the adr

Re: [Qgis-developer] Geocoding plugin: a good case for merge

2016-06-11 Thread mederic . ribreux
Hello, It could also be very interesting to have one or more Processing module(s) for geocoding (natives QGIS "algorithms"). We could then chain this with other algorithms (find all objects of a layer intersecting a 500m buffer from the positions of the adresses in a list for example). Of cour