<div dir="ltr"><div>Hi Larry<br><br></div>+1 for your proposal !<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-01-26 Larry Shaffer <span dir="ltr"><<a href="mailto:larrys@dakotacarto.com" target="_blank">larrys@dakotacarto.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi,<br><br></div>So, to recap:<br><br>+1 to remove the annoying, interrupting new name dialog,<br>and +1 for moving its functionality to the top of the Composition Panel<br>
<div><div><div><div class="gmail_extra">
<br></div><div class="gmail_extra">A non-editable field displaying the name and a simple edit button next to it that opens up the same rename dialog as is found in the Composer Manager would be all that is needed. I suggest the continued use of the rename dialog since it offers validation that the name is unique among existing composers names, and allows for quickly building a name off of an existing name.<br clear="all">
</div><div class="gmail_extra"><div><br></div><div>If this change (not really a feature) will be allowed for 2.2 release, I can commit the work today.<br></div><div><br></div><div>Regards,<br></div><div><br>Larry</div><div>
<div class="h5">
<br><br><div class="gmail_quote">On Sat, Jan 25, 2014 at 4:13 PM, Larry Shaffer <span dir="ltr"><<a href="mailto:larrys@dakotacarto.com" target="_blank">larrys@dakotacarto.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">Hi,<br><div><div class="gmail_extra"><br></div><div class="gmail_extra">I specifically added that dialog, since so many times my composers resulted in unrecognizable names. I believe without it many users will suffer from this as well. However, I'm not necessarily keen on its implementation, but wish not to remove the functionality, just move it elsewhere. The new naming functionality (e.g. to quickly base a name off of an existing composer, etc.) is already part of Composer Manager, so nothing needs changed there.<br>
<br></div><div class="gmail_extra">A better solution when creating a new composer, and gently nudging the user to set a name for it, might be to move the dialog's widget functionality to a 'Name' field at the top of the Composition panel.<br>
<br>Then, when a user creates a new composer and the main window is shown, set keyboard focus to that field and set its background to a color to signify the user should consider entering a unique name (e.g. pale yellow). The background could be on a singleshot timer so that it fades out after a bit.<br>
<br>This would only be when creating a new Composer; and, since the field could already have a generated name inputted, the user can just choose to ignore it. This also means that GUI scripts don't have to deal with the current interim dialog.<br clear="all">
</div><div class="gmail_extra"><div><br></div><div>Regards,<br></div><div><br>Larry</div>
<br><br><div class="gmail_quote">On Sat, Jan 25, 2014 at 2:54 AM, Andreas Neumann <span dir="ltr"><<a href="mailto:a.neumann@carto.net" target="_blank">a.neumann@carto.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi,<br>
<br>
+1 for removing it. Maybe an auto-generated name that does not clash<br>
with existing composer names would be useful - which the user can later<br>
on rename.<br>
<br>
The user will have to set paper format anyway. In this step he can also<br>
set the composer name.<br>
<br>
Andreas<br>
<br>
Am 25.01.2014 09:04, schrieb kimaidou:<br>
> Hi Martin<br>
><br>
> +1 for removing it, as it is a step I usually skip too. But only if we<br>
> provide a input field in the composer properties tab to allow to add/change<br>
> the name directly in the opened composer (above the paper size for<br>
> example). This way I won't need to open the composer manager only to rename<br>
> it afterwards.<br>
><br>
> Michael<br>
><br>
><br>
> 2014/1/25 Martin Dobias <<a href="mailto:wonder.sk@gmail.com" target="_blank">wonder.sk@gmail.com</a>><br>
><br>
>> Hi<br>
>><br>
>> Is there any good reason for the small pop-up dialog asking for<br>
>> composer name when user wants to create a new composer? There is the<br>
>> composer manager where the composer can be renamed at any time, so to<br>
>> me it looks like an unnecessary step and I would be happy to remove it<br>
>> :-)<br>
>><br>
>> Regards<br>
>> Martin<br>
>> _______________________________________________<br>
>> Qgis-developer mailing list<br>
>> <a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Qgis-developer mailing list<br>
> <a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
><br>
<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</blockquote></div><br></div></div></div>
</blockquote></div><br></div></div></div></div></div></div></div>
<br>_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br></blockquote></div><br></div>