Hi, So, to recap:
+1 to remove the annoying, interrupting new name dialog, and +1 for moving its functionality to the top of the Composition Panel 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. If this change (not really a feature) will be allowed for 2.2 release, I can commit the work today. Regards, Larry On Sat, Jan 25, 2014 at 4:13 PM, Larry Shaffer <[email protected]>wrote: > Hi, > > 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. > > 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. > > 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. > > 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. > > Regards, > > Larry > > > On Sat, Jan 25, 2014 at 2:54 AM, Andreas Neumann <[email protected]>wrote: > >> Hi, >> >> +1 for removing it. Maybe an auto-generated name that does not clash >> with existing composer names would be useful - which the user can later >> on rename. >> >> The user will have to set paper format anyway. In this step he can also >> set the composer name. >> >> Andreas >> >> Am 25.01.2014 09:04, schrieb kimaidou: >> > Hi Martin >> > >> > +1 for removing it, as it is a step I usually skip too. But only if we >> > provide a input field in the composer properties tab to allow to >> add/change >> > the name directly in the opened composer (above the paper size for >> > example). This way I won't need to open the composer manager only to >> rename >> > it afterwards. >> > >> > Michael >> > >> > >> > 2014/1/25 Martin Dobias <[email protected]> >> > >> >> Hi >> >> >> >> Is there any good reason for the small pop-up dialog asking for >> >> composer name when user wants to create a new composer? There is the >> >> composer manager where the composer can be renamed at any time, so to >> >> me it looks like an unnecessary step and I would be happy to remove it >> >> :-) >> >> >> >> Regards >> >> Martin >> >> _______________________________________________ >> >> Qgis-developer mailing list >> >> [email protected] >> >> http://lists.osgeo.org/mailman/listinfo/qgis-developer >> >> >> > >> > >> > >> > _______________________________________________ >> > Qgis-developer mailing list >> > [email protected] >> > http://lists.osgeo.org/mailman/listinfo/qgis-developer >> > >> >> _______________________________________________ >> Qgis-developer mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/qgis-developer >> > >
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
