Exactly - these are good terms to use - "disabled rule" and "invisible
rule". Thanks for suggesting these, Andreas. Alexandre - could you
please note this in the ticket?
Andreas
On 19.06.2015 16:33, Matthias Kuhn wrote:
Just my 2 cents on a topic I know nothing about :)
... or we can have a "disable rule" and an "invisible rule". Disabled
rules go to ELSE, invisible rules don't go to ELSE.
Cheers
On 06/19/2015 04:13 PM, Alexandre Neto wrote:
So, can I open a ticket?
Alexandre
On Fri, Jun 19, 2015 at 12:50 PM, Andreas Neumann
<[email protected] <mailto:[email protected]>> wrote:
In my opinion this is a bug. I agree that by switching off the
rule should not make the features fall into the ELSE rule. At
least from a usability point of view. Or we need to ELSE rules -
a "TRUE ELSE" rule that behaves like now and an "ELSE" rule that
behaves like the users expect it to behave.
Andreas
On 19.06.2015 13:36, Etienne Trimaille wrote:
I've this kind of bug too.
If you create a categorized symbology, apply the change and then
switch to a ruled-based symbology (keeping the previous rules),
you will see that the ELSE statement will draw features twice.
Enable "show feature count" to check.
I didn't check if there is a ticket for that.
2015-06-19 13:18 GMT+02:00 Alexandre Neto <[email protected]
<mailto:[email protected]>>:
Indeed Nathan,
But do you thinks that is what you were expecting? when you
turn the "layer" off?
Alexandre
On Fri, Jun 19, 2015 at 12:08 PM, Nathan Woodrow
<[email protected] <mailto:[email protected]>> wrote:
I would say they are getting skipped in the rule check
so fall into the else rule.
On Fri, 19 Jun 2015 9:05 pm Alexandre Neto
<[email protected] <mailto:[email protected]>>
wrote:
Using the rule-based symbology with several rules
and an ELSE expression. If you, in map canvas
legend, set a rule "layer" to invisible, all it's
features will be represented with the ELSE Symbol.
Not sure if this is the expected behaviour. I would
expect that those feature would simply became invisible.
Should I open a ticket?
Thanks,
Alexandre Neto
_______________________________________________
Qgis-developer mailing list
[email protected]
<mailto:[email protected]>
http://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
Qgis-developer mailing list
[email protected]
<mailto:[email protected]>
http://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
Qgis-developer mailing list
[email protected] <mailto:[email protected]>
http://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
Qgis-developer mailing list
[email protected]
<mailto:[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