I also agree that your first solution is the clearest one. I generally avoid hiding the default options ore making the opposite option of the one checkable by the user not evident.
giovanni Inviato da dispositivo mobile Il giorno 28/lug/2012 23.07, "Larry Shaffer" <[email protected]> ha scritto: > On Sat, Jul 28, 2012 at 6:14 AM, Nathan Woodrow <[email protected]> > wrote: > > I would vote for this one http://goo.gl/IfZbf as, like you said, > > required less thinking on the users part. It is also more explicit > > then the second one as the user isn't sure what unticking "Current > > Extent" really means. > > > > - Nathan > > Radim, > > I also like the second choice, with extra grouping. Coming from the > perspective of someone who doesn't use the histogram features very > often, I found http://goo.gl/IfZbf to be fairly straightforward. > > Also, the condensed version has multiple radio button groups within > the same group box, which I not only found a bit confusing, but also > would require further coding or sub-layouts to create isolated radio > button groups, whereas the extra group box layout does that > automatically. > > Larry > > > > On Sat, Jul 28, 2012 at 10:00 PM, Radim Blazek <[email protected]> > wrote: > >> Hi, > >> I am working on 2-98% cumulative pixel count cut (raster stretch > >> min/max, stdev alternative). Adding that option into raster > >> properties, I found the "Load min/max values" (http://goo.gl/xl2Ti) > >> group a bit confusing, it was mixing method, extent and accuracy, all > >> in one group: > >> * Estimate - accuracy > >> * Actual - accuracy > >> * CurrentExtent - extent > >> * Standard deviation - method > >> > >> Following QGIS HIG "Group related elements using group boxes" I added > >> groups for extent and accuracy (logically, there should be another one > >> for method, but that would result in another group header just under > >> "Load min/max values"): http://goo.gl/IfZbf > >> From that widget it is clear I believe, what each checkbox means and > >> how do they work together. It is crowded, however. > >> > >> I simplified it removing the groups and checkboxes for defaults: > >> http://goo.gl/4XmpR > >> It looks better but does not follow HIG and user must think more to > >> imagine what are opposites of "Current extent" and "Estimate". > >> > >> Which one is preferred? Do you have better idea? > >> > >> With 3 parameters as input, it is also impossible to have loading > >> min/max as an action in histogram tab (commented for now) until we add > >> all combinations. > >> > >> Radim > >> _______________________________________________ > >> 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
