I retract my comments completely until I get a chance to think it all through
again...
Tom
-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Changing-ergonomy-of-the-visibility-of-layers-inside-groups-tp52958
Plugin Semi-Automatic Classification Plugin approval by lucasupervised.
The plugin version "[284] Semi-Automatic Classification Plugin 5.2.1" is now
approved
Link: http://plugins.qgis.org/plugins/SemiAutomaticClassificationPlugin/
___
Qgis-developer mai
Plugin Semi-Automatic Classification Plugin approval by lucasupervised.
The plugin version "[284] Semi-Automatic Classification Plugin 5.2.1" is now
unapproved
Link: http://plugins.qgis.org/plugins/SemiAutomaticClassificationPlugin/
___
Qgis-developer m
Plugin Semi-Automatic Classification Plugin approval by lucasupervised.
The plugin version "[284] Semi-Automatic Classification Plugin 5.2.1" is now
unapproved
Link: http://plugins.qgis.org/plugins/SemiAutomaticClassificationPlugin/
___
Qgis-developer m
On 11/16/2016 02:44 PM, Even Rouault wrote:
>> Another scenario would be:
>>
>> When clicking, the group toggle between unchecked, partially checked,
>> checked. At the same time it caches the state for all subitems to
>> restore the partially checked state when switching to this.
>>
>> At any time
On Wed, Nov 16, 2016 at 4:22 PM, Matthias Kuhn wrote:
> On 11/16/2016 03:48 PM, Alessandro Pasotti wrote:
> > On Wed, Nov 16, 2016 at 3:07 PM, Matthias Kuhn >
> > It might be a problem in the test, but a segmentation fault could be a
> > signal of something more serious in the core on in the bin
Le mercredi 16 novembre 2016 15:12:27, Tom Chadwin a écrit :
> > You click on G ==> it becomes partially checked, and you restore
>
> StatePartial
> (ie A is unchecked and B is checked)
>
> [and earlier posts]
>
> I don't think I agree with this. I'll try to express how I would expect it
> to wo
On 11/16/2016 03:48 PM, Alessandro Pasotti wrote:
> On Wed, Nov 16, 2016 at 3:07 PM, Matthias Kuhn
> It might be a problem in the test, but a segmentation fault could be a
> signal of something more serious in the core on in the bindings.
>
> From the build history, this particular test does not
On Wed, Nov 16, 2016 at 3:07 PM, Matthias Kuhn wrote:
> Following the conversation from
> https://github.com/qgis/QGIS/commit/89d4998 , this is an announcement
> to notify that the PyQgsOfflineEditingWFS has been disabled on the
> Travis builds.
>
> Work has been underway to remove "noisy" tests
+1 would be a wonderful improvements, I agree with the three state
implementation.
Luigi Pirelli
**
* Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT com
* LinkedIn: https://www.linkedi
> You click on G ==> it becomes partially checked, and you restore
StatePartial
(ie A is unchecked and B is checked)
[and earlier posts]
I don't think I agree with this. I'll try to express how I would expect it
to work:
- the check state of a group is determined entirely by the check state of
Following the conversation from
https://github.com/qgis/QGIS/commit/89d4998 , this is an announcement
to notify that the PyQgsOfflineEditingWFS has been disabled on the
Travis builds.
Work has been underway to remove "noisy" tests from Travis which cause
false alarms and these tests regularly fail
Hi all,
Jumping in... Quite reluctant at first, I think it's indeed a very nice
improvement.
Matthias' idea is quite nice and turns off my concerns.
I would prefer first approach (switching brtween partial and checked or
unchecked) as I find it more intuitive and also more practical: one
click o
> Another scenario would be:
>
> When clicking, the group toggle between unchecked, partially checked,
> checked. At the same time it caches the state for all subitems to
> restore the partially checked state when switching to this.
>
> At any time, when a subitems check state is changed, all par
On 11/16/2016 01:54 PM, Even Rouault wrote:
>> The visualisation could still be tri-state, I think
>>
>> * Unchecked
>> * Checked (All subitems checked)
>> * Semi-checked (Checked but some sub-items are invisible)
>>
>> Clicking would then switch between either Unchecked and Semi-Checked or
>> Un
> The visualisation could still be tri-state, I think
>
> * Unchecked
> * Checked (All subitems checked)
> * Semi-checked (Checked but some sub-items are invisible)
>
> Clicking would then switch between either Unchecked and Semi-Checked or
> Unchecked and Checked depending on the subitems.
>
T
> Grey out is already used to indicate that a checked layer is currently
> out of its scale range of visibility (hence not visible). so it may be good
> to keep greying layers when they "should" be visible but another option
> makes them not rendered.
>
Good suggestion
--
Spatialys - Geospatia
> I think this would be a good improvement to the usability of the legend
> groups.
>
> Does it make sense to add a right-click action to maintain the possibility
> of hierarchical/recursive selection of the group items?
Yes, users might not necessarily be aware of the Ctrl+click shortcut. For th
Sounds good to me.
On 11/15/2016 11:34 AM, Even Rouault wrote:
> One effect of this change is that there wouldn't be anymore a tri-state for a
> group. It is either checked or unchecked.
The visualisation could still be tri-state, I think
* Unchecked
* Checked (All subitems checked)
* Semi-che
On 15 November 2016 at 20:34, Even Rouault wrote:
> Hi,
>
> I've been involved in discussions about improving/changing how visibility of
> layers (or groups) is handled when they are inside groups. Currently if you
> check/uncheck a group, this recursively checks/unchecks all its items (layers
> o
Hi Richard,
What the trash button does is
vl.beginEditCommand( "Delete Selected Features" )
vl.deleteSelectedFeatures()
vl.endEditCommand()
This makes me think, that the "with edit" construct could actually wrap
things into a single edit command as well.
Matthias
On 11/14/2016 04:55 PM, Richar
Bump...
Richard
On 14-11-16 16:55, Richard Duivenvoorde wrote:
Hi Dev's,
having a small dataset of 300 features (from an online service).
I want to quickly remove most/all of those features, request a new set
an put them in the same vectorlayer (in a python plugin).
All ok, untill you acti
22 matches
Mail list logo
