Re: [QGIS-Developer] Suggestion for changelog entry about default values

[Daan Goedkoop]

Hello Etienne,

I've tried it now, but after clicking Submit I got an error about "too
many redirects" and now I can't see the entry anymore at all. Strange.

Regards,
Daan

2018-02-22 7:52 GMT+01:00 Etienne Trimaille :
> Hi Daan,
>
> You should be able to create an account on changelog.qgis.org and then edit
> the entry. Then it will go in the pending queue for a review.
>
> Contributions on the changelog are more than welcome, there is a lot of work
> to do ;-)
> Thanks for your contribution.
>
> Regards,
> Etienne
>
> 2018-02-22 9:47 GMT+03:00 Daan Goedkoop :
>>
>> Hello,
>>
>> As per the discussion of this bug report:
>> https://issues.qgis.org/issues/17990, could a text be added to this
>> changelog entry:
>>
>> http://changelog.qgis.org/en/qgis/version/3.0.0/#improved-handling-of-defaults
>> ?
>>
>> For example: "This also means that, after certain editing operations
>> (e.g. copy-paste, split features etc.) attributes will now be set to
>> their default value, if applicable."
>>
>> Kind regards,
>>
>> Daan Goedkoop
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Suggestion for changelog entry about default values

[Etienne Trimaille]

Hi Daan,

You should be able to create an account on changelog.qgis.org and then edit
the entry. Then it will go in the pending queue for a review.

Contributions on the changelog are more than welcome, there is a lot of
work to do ;-)
Thanks for your contribution.

Regards,
Etienne

2018-02-22 9:47 GMT+03:00 Daan Goedkoop :

> Hello,
>
> As per the discussion of this bug report:
> https://issues.qgis.org/issues/17990, could a text be added to this
> changelog entry:
> http://changelog.qgis.org/en/qgis/version/3.0.0/#improved-
> handling-of-defaults
> ?
>
> For example: "This also means that, after certain editing operations
> (e.g. copy-paste, split features etc.) attributes will now be set to
> their default value, if applicable."
>
> Kind regards,
>
> Daan Goedkoop
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Suggestion for changelog entry about default values

[Daan Goedkoop]

Hello,

As per the discussion of this bug report:
https://issues.qgis.org/issues/17990, could a text be added to this
changelog entry:
http://changelog.qgis.org/en/qgis/version/3.0.0/#improved-handling-of-defaults
?

For example: "This also means that, after certain editing operations
(e.g. copy-paste, split features etc.) attributes will now be set to
their default value, if applicable."

Kind regards,

Daan Goedkoop
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Concerns re UX of new "duplicate features" actions in 2.99

[Nyall Dawson]

On 22 February 2018 at 07:15, David Signer  wrote:
> Hi Nyall
>
> It's okay for me, when you merge it to be save and we remove it, when the
> issue is resolved.
>
> But I'll remove the part that the duplicate functions toggles the edit mode
> anyway.
> So in case there will be still the action to duplicate on a not editable
> layer somewhere (what it shouldn't) it won't damage the layer.

Thank you -- merged. Happy to help with the rework if you need advice!

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Concerns re UX of new "duplicate features" actions in 2.99

[David Signer]

Hi Nyall  
  
It's okay for me, when you merge it to be save and we remove it, when the issue 
is resolved.  
  
But I'll remove the part that the duplicate functions toggles the edit mode 
anyway.   
So in case there will be still the action to duplicate on a not editable layer 
somewhere (what it shouldn't) it won't damage the layer.  
  
Thanks and regards  
Dave  
  

> On 22 February 2018 at 06:20, Matthias Kuhn  wrote:   
>  > On 02/21/2018 08:55 PM, Nyall Dawson wrote:   
>  >> On 22 February 2018 at 05:24, Matthias Kuhn  wrote:   
>  >>> Hi Dave, hi Nyall,   
>  >>>   
>  >>> Thanks for all your thoughts and work on this. The approach that is   
>  >>> currently being developed sounds like a very reasonable one given the   
>  >>> remaining time for 3.0.   
>  >>>   
>  >> In the meantime, I'd like to merge that PR. 3.0 is only a couple of   
>  >> hours away and it makes me very nervous having this feature exposed   
>  >> still. Can I merge, and then we can address whether to remove the flag   
>  >> when the changes have landed?   
>  >   
>  > I don't know enough about it myself, I only followed this topic 
> marginally.   
>  >   
>  > It would be good to get the green flag for it from Dave and Andreas if   
>  > somehow possible.   
>   
>  Yes, ideally... but also (with full respect to all involved), in its   
>  current form this feature is just too dangerous to have in the   
>  release. I would not feel comfortable at all in rolling out 3.0 in my   
>  customer's organizations with the knowledge that a single accidental   
>  slip of the mouse can permanently damage a non-editable layer.   
>   
>  That's why I would greatly prefer to hide it now, and then un-hide if   
>  the issues are resolved before release.   
>   
>  "Better safe than sorry" and all that :)   
>   
>  Nyall   
>  ___   
>  QGIS-Developer mailing list   
>  QGIS-Developer@lists.osgeo.org   
>  List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer   
>  Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
  
  
-  


David Signer  


Programmer OPENGIS.CH  


Wülflingerstrasse 213  


CH - 8408  Winterthur  


+ 41 (0) 78 766 13 03  


-  


  

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Concerns re UX of new "duplicate features" actions in 2.99

[Matthias Kuhn]

Hi Dave, hi Nyall,

Thanks for all your thoughts and work on this. The approach that is
currently being developed sounds like a very reasonable one given the
remaining time for 3.0.


Another idea I had to handle things like this was an "activate
condition" for actions. The activate condition for the duplicate feature
action could be a simple `@layer_editable`.

The tricky thing is, that variables (or even expression functions) used
within such a construct will need to be notifiable (e.g. here upon layer
edit state change, but in theory it could depend on other things like
`selected_feature_count(@layer) > 2`), so the expression engine knows
when an expression needs to be re-evaluated.

It will be a non-trivial thing to do and I'm not yet convinced it's
worth it, but I could imagine that we find other areas in QGIS where
such an interactive machinery to enable button states or change labels
interactively based on expressions can come in handy.

Enjoy Madeira, I miss you all !!

Matthias


On 02/21/2018 03:55 PM, David Signer wrote:
> Hi Nyall
>
> I'll start with it today. So possibly it's done before the 23th.
>
> We could keep it as an Action, only enabled when the layer is editable.
> This would include an attribute of MapLayerAction, if it should be
> enabled only in editable mode or always (first case for the
> duplication-action). The user actions would need such a attribute as
> well. 
> Probably we could integrate this attribute as another scope-value, and
> use the scopes as well for the MapLayerActions.
> Then we need to decide on what scopes it should be displayed:
> - Canvas (in the main toolbar)
> - Layer (in the toolbar of attribute list)
> - Feature (in the actions of attribute form, right click on a feature
> in the form view, right click on the feature on canvas)
> - Field (right click on a field in row of attribute table, right click
> on field at identify result panel)
>
> What do you think?
>
> Thanks for the ini-configuration anyway. Probably we will need it as
> well. 
>
> Regards
> David
>
> /21 February 2018 05:27 Nyall Dawson  wrote:/
>
> On 19 February 2018 at 16:24, Nyall Dawson wrote:
> > On 15 February 2018 at 03:16, David Signer wrote:
> >> Dear all
> >>
> >> I agree (and I guess everyone else does), that it's not okay
> that this
> >> feature is enabled when the layers are not in editable mode. I
> already
> >> started to fix that, but because of time I had to decide to
> finish it next
> >> week.
> >>
> >> Anyway, there is still the question, where it should appear.
> IMHO it should
> >> be everywhere, where you can add and delete features. If it's a
> MapTool it
> >> could be there as well, I think. I'll have to think about that.
> >
> > Thanks for your flexibility here!
> >
> > What's the chance of getting this resolved before 3.0 final? If we
> > can't, can we please ifdef this out for 3.0 release and defer to
> 3.2?
> >
>
> In https://github.com/qgis/QGIS/pull/6399 I implement a advanced
> settings option, "tools\showDuplicateFeatureActions" to control
> whether these actions are shown. By default it's off, but interested
> organisations can set the flag in their qgis_global_settings.ini to
> show these actions.
>
> I think that's a fair approach - it means that users/organisations
> which require this feature can still use it in 3.0, whilst at the
> same
> time avoiding exposing the functionality to users by default until it
> is refined.
>
> Nyall
>
>
>
> -
>
> David Signer
>
> Programmer OPENGIS.CH
>
> Wülflingerstrasse 213
>
> CH - 8408  Winterthur
>
> + 41 (0) 78 766 13 03
>
> -
>
>
>
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Concerns re UX of new "duplicate features" actions in 2.99

[Nyall Dawson]

On 22 February 2018 at 00:55, David Signer  wrote:

> We could keep it as an Action, only enabled when the layer is editable.
> This would include an attribute of MapLayerAction, if it should be enabled
> only in editable mode or always (first case for the duplication-action). The
> user actions would need such a attribute as well.
> Probably we could integrate this attribute as another scope-value, and use
> the scopes as well for the MapLayerActions.
> Then we need to decide on what scopes it should be displayed:
> - Canvas (in the main toolbar)
> - Layer (in the toolbar of attribute list)
> - Feature (in the actions of attribute form, right click on a feature in the
> form view, right click on the feature on canvas)
> - Field (right click on a field in row of attribute table, right click on
> field at identify result panel)

Hiding the action everywhere when a layer is non-editable is a good
move. I'd also like to see it completely removed (regardless of
editable status) from:

1. The identify results right click menu and results tree view (I
think that all actions with a "only show in editable mode" flag should
be skipped from these places - the identify tool is typically a "view"
tool, not an edit tool)
2. The menu bar in the attribute form dialog (at least for newly
created features)

Thanks for your responsiveness on this!

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Concerns re UX of new "duplicate features" actions in 2.99

[Nyall Dawson]

On 22 February 2018 at 06:20, Matthias Kuhn  wrote:
> On 02/21/2018 08:55 PM, Nyall Dawson wrote:
>> On 22 February 2018 at 05:24, Matthias Kuhn  wrote:
>>> Hi Dave, hi Nyall,
>>>
>>> Thanks for all your thoughts and work on this. The approach that is
>>> currently being developed sounds like a very reasonable one given the
>>> remaining time for 3.0.
>>>
>> In the meantime, I'd like to merge that PR. 3.0 is only a couple of
>> hours away and it makes me very nervous having this feature exposed
>> still. Can I merge, and then we can address whether to remove the flag
>> when the changes have landed?
>
> I don't know enough about it myself, I only followed this topic marginally.
>
> It would be good to get the green flag for it from Dave and Andreas if
> somehow possible.

Yes, ideally... but also (with full respect to all involved), in its
current form this feature is just too dangerous to have in the
release. I would not feel comfortable at all in rolling out 3.0 in my
customer's organizations with the knowledge that a single accidental
slip of the mouse can permanently damage a non-editable layer.

That's why I would greatly prefer to hide it now, and then un-hide if
the issues are resolved before release.

"Better safe than sorry" and all that :)

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Concerns re UX of new "duplicate features" actions in 2.99

[Matthias Kuhn]

On 02/21/2018 08:55 PM, Nyall Dawson wrote:
> On 22 February 2018 at 05:24, Matthias Kuhn  wrote:
>> Hi Dave, hi Nyall,
>>
>> Thanks for all your thoughts and work on this. The approach that is
>> currently being developed sounds like a very reasonable one given the
>> remaining time for 3.0.
>>
> In the meantime, I'd like to merge that PR. 3.0 is only a couple of
> hours away and it makes me very nervous having this feature exposed
> still. Can I merge, and then we can address whether to remove the flag
> when the changes have landed?

I don't know enough about it myself, I only followed this topic marginally.

It would be good to get the green flag for it from Dave and Andreas if
somehow possible.

Regards
Matthias
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Concerns re UX of new "duplicate features" actions in 2.99

[Nyall Dawson]

On 22 February 2018 at 05:24, Matthias Kuhn  wrote:
> Hi Dave, hi Nyall,
>
> Thanks for all your thoughts and work on this. The approach that is
> currently being developed sounds like a very reasonable one given the
> remaining time for 3.0.
>

In the meantime, I'd like to merge that PR. 3.0 is only a couple of
hours away and it makes me very nervous having this feature exposed
still. Can I merge, and then we can address whether to remove the flag
when the changes have landed?

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Changelog site upgrade

[Tim Sutton]

Hi

> On 21 Feb 2018, at 19:18, Richard Duivenvoorde  wrote:
> 
> On 21-02-18 17:01, Martin Dobias wrote:
>> Hi Tim
>> 
>> On Wed, Feb 21, 2018 at 1:28 PM, Tim Sutton > > wrote:
>> 
>>Hi
>> 
>>Thanks you for your patience - the server upgrade is complete and
>>changelog is back online. Please feel free to help work on the
>>changelog for the release!
>> 
>> 
>> Thanks for the update! Just wondering, is there a way to add a new
>> category in the changelog? I thought all 3D-related features could get a
>> dedicated category, but I can't see a way how to add a category in the
>> web interface...
> 
> Just added '3D Features/3d-features' as category.

Thanks Richard!

Regards

Tim

> 
> Regards,
> 
> Richard

—







Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux
IRC: timlinux on #qgis at freenode.net



signature.asc
Description: Message signed with OpenPGP
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS 3.0 Sluggish on MacOS 10.13 with Retina Display

[Jeremy Palmer]

Hi Nyall,

On Wed, Feb 21, 2018 at 6:51 PM, Nyall Dawson 
wrote:
>
>
> I'm just saying that there's nothing QGIS specific there - so there's
> no clues there wherever it's a generic Qt issue or a QGIS regression.
>

I'm using xcode's instruments, but I've never really developed in any code
on MacOSX before. I will see what else can be dumped.


>
> I'm not familiar with OSX - can you set the monitor resolution
> manually? something like 1280 x 800 would be a good test.


I set the screen scale to 1280 x 800. It made some improvement in speed,
but QGIS 3.0 still is running much slower than 2.18.

I also tried enabling the Low Resolution mode for the app bundle as per
[1]. This setting forces the device pixel ratio to 1 from 2 for HiDPI
supported applications. e.g
qgis.utils.iface.mainWindow().devicePixelRatio() = 1. This of course forces
the UI to low resolution and reverses all of the QGIS 3.0 SVG icons work :( The
results were:

1. The QGIS 3.0 mapcanvas UI interactions seemed smoother due to the
increased frame-rate for redrawing the zoom rubberband box or moving the
the cursor.
2. But, the canvas redraws were still just and slow as a device pixel ratio
of 1. i.e The profiling still showed the same amount of CPU time

Here's the results of my benchmarking:

[image: Inline image 1]

Note: canvas size was determined using qgis.utils.iface.mapCanvas().size()

Before I proceed with further profiling it would be good to know if other
mac developers also see performance slowdowns like I do?

Cheers,
Jeremy

* [1] https://support.apple.com/en-nz/HT202471
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Changelog site upgrade

[Richard Duivenvoorde]

On 21-02-18 17:01, Martin Dobias wrote:
> Hi Tim
> 
> On Wed, Feb 21, 2018 at 1:28 PM, Tim Sutton  > wrote:
> 
> Hi
> 
> Thanks you for your patience - the server upgrade is complete and
> changelog is back online. Please feel free to help work on the
> changelog for the release!
> 
>  
> Thanks for the update! Just wondering, is there a way to add a new
> category in the changelog? I thought all 3D-related features could get a
> dedicated category, but I can't see a way how to add a category in the
> web interface...

Just added '3D Features/3d-features' as category.

Regards,

Richard
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Changelog site upgrade

[Martin Dobias]

Hi Tim

On Wed, Feb 21, 2018 at 1:28 PM, Tim Sutton  wrote:

> Hi
>
> Thanks you for your patience - the server upgrade is complete and
> changelog is back online. Please feel free to help work on the changelog
> for the release!
>
>
Thanks for the update! Just wondering, is there a way to add a new category
in the changelog? I thought all 3D-related features could get a dedicated
category, but I can't see a way how to add a category in the web
interface...

Cheers
Martin
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Data defined @symbol_color outlines

[McDonaldR]

Hi List

This issue (https://issues.qgis.org/issues/15132) refers to using the 
@symbol_color function to make the outline of graduated/categorised features 
the same colour as the fill.  There is a fix by Nyall from over a year ago but 
I wonder if there has been a regression?

I am using both the latest 2.99 master and 2.18.16 64-bit versions on Windows 7 
and if I render a polygon layer using the categorised or graduated renderer and 
set the outline colour using @symbol_color then the legend doesn't reflect the 
style shown on the map. The features are rendered correctly (I like using 
"darker(@symbol_color,150)") on the map canvas and the print composer but the 
legend in the table of contents and on the composer layout show the default 
outline colour.

The only way I can get the legend to update is to set the outline/stroke colour 
to the fill colour for each category and then make it slightly darker - not too 
much of a hassle if there are a few but a hassle if there are more than that.

Can anyone else confirm this?  And has there been a regression or was the fix 
for something slightly different?

Thanks in advance

Ross

Ross McDonald | GIS Data Coordinator | Angus Council, People, IT | Angus House, 
Orchardbank Business Park, Sylvie Way, Forfar DD8 1AT | t: 01307 476419


This message is strictly confidential. If you have received this in error, 
please inform the sender and remove it from your system. If received in error 
you may not copy, print, forward or use it or any attachment in any way. This 
message is not capable of creating a legal contract or a binding representation 
and does not represent the views of Angus Council. Emails may be monitored for 
security and network management reasons. Messages containing inappropriate 
content may be intercepted. Angus Council does not accept any liability for any 
harm that may be caused to the recipient system or data on it by this message 
or any attachment.
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] keyPressEvent on QgsMapTool

[Poltini Roberto]

Hi devs,
   I am using an object derived by QgsMapTool class (python, qgis 2.18 on 
window).
I need to use the keyPressEvent function of QgsMapTool.
I cannot receive any event if I press some keys for example “a”, “c”, “d”, “p”, 
“x”, “y” keys.
The other keys works fine.
Is there anybody who can help me ?

Thank you

Roberto Poltini

Per essere informati sulle novità del Gruppo Iren, vi invitiamo a registrarvi 
alla nostra mailing list, all’indirizzo 
"http://www.gruppoiren.it/; .

È possibile, inoltre, avanzare nuove idee e progetti per il territorio e 
seguire quelli già attivi nei Comitati Territoriali del Gruppo Iren, 
consultando "http://www.Irencollabora.it;

You can also suggest new ideas and initiatives for the territory and view those 
already active in the Iren Group Territorial Committees 
"http://www.Irencollabora.it;

Le informazioni contenute nella presente comunicazione e i relativi allegati 
possono essere riservate e sono, comunque, destinate esclusivamente alle 
persone o alla Società sopraindicati. La diffusione, distribuzione e/o 
copiatura del documento trasmesso da parte di qualsiasi soggetto diverso dal 
destinatario è proibita, sia ai sensi dell’art. 616 c.p. , che ai sensi del 
D.Lgs. n. 196/2003. Se avete ricevuto questo messaggio per errore, vi preghiamo 
di distruggerlo e di informare immediatamente il mittente.


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Concerns re UX of new "duplicate features" actions in 2.99

[David Signer]

Hi Nyall  
  
I'll start with it today. So possibly it's done before the 23th.  
  
We could keep it as an Action, only enabled when the layer is editable.  
This would include an attribute of MapLayerAction, if it should be enabled only 
in editable mode or always (first case for the duplication-action). The user 
actions would need such a attribute as well.   
Probably we could integrate this attribute as another scope-value, and use the 
scopes as well for the MapLayerActions.  
Then we need to decide on what scopes it should be displayed:  
- Canvas (in the main toolbar)  
- Layer (in the toolbar of attribute list)  
- Feature (in the actions of attribute form, right click on a feature in the 
form view, right click on the feature on canvas)  
- Field (right click on a field in row of attribute table, right click on field 
at identify result panel)  
  
What do you think?  
  
Thanks for the ini-configuration anyway. Probably we will need it as well.   
  
Regards  
David  

> On 19 February 2018 at 16:24, Nyall Dawson  wrote:   
> > On 15 February 2018 at 03:16, David Signer  wrote:   
> >> Dear all   
> >>   
> >> I agree (and I guess everyone else does), that it's not okay that this   
> >> feature is enabled when the layers are not in editable mode. I already   
> >> started to fix that, but because of time I had to decide to finish it next 
> >>   
> >> week.   
> >>   
> >> Anyway, there is still the question, where it should appear. IMHO it 
> >> should   
> >> be everywhere, where you can add and delete features. If it's a MapTool it 
> >>   
> >> could be there as well, I think. I'll have to think about that.   
> >   
> > Thanks for your flexibility here!   
> >   
> > What's the chance of getting this resolved before 3.0 final? If we   
> > can't, can we please ifdef this out for 3.0 release and defer to 3.2?   
> >   
>   
> In https://github.com/qgis/QGIS/pull/6399 I implement a advanced   
> settings option, "tools\showDuplicateFeatureActions" to control   
> whether these actions are shown. By default it's off, but interested   
> organisations can set the flag in their qgis_global_settings.ini to   
> show these actions.   
>   
> I think that's a fair approach - it means that users/organisations   
> which require this feature can still use it in 3.0, whilst at the same   
> time avoiding exposing the functionality to users by default until it   
> is refined.   
>   
> Nyall
  
  
-  


David Signer  


Programmer OPENGIS.CH  


Wülflingerstrasse 213  


CH - 8408  Winterthur  


+ 41 (0) 78 766 13 03  


-  


  

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1416] Breeder Map approval notification.

[noreply]

Plugin Breeder Map approval by pcav.
The plugin version "[1416] Breeder Map 0.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/BreederMap/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Changelog site upgrade

[Tim Sutton]

Hi

Thanks you for your patience - the server upgrade is complete and changelog is 
back online. Please feel free to help work on the changelog for the release!

Regards

Tim

> On 21 Feb 2018, at 12:10, Tim Sutton  wrote:
> 
> Hi All
> 
> NOTICE: ESPECIALLY FOR THOSE WORKING ON THE CHANGELOG AT THE HACKFEST...
> 
> We are going to push out some changes to the live changelog site this 
> afternoon - the site will be unavailable (hopefully just for a few minutes) 
> while I do the upgrade.
> 
> The upgrade will happen at 12h45 Madeira time, 14h45 South Africa time, 13h45 
> CET time.
> 
> I will post another notice here when the upgrade is complete.
> 
> Regards
> 
> Tim
> 
> 
> —
> 
> 
> 
> 
> 
> 
> 
> Tim Sutton
> 
> Co-founder: Kartoza
> Project chair: QGIS.org 
> 
> Visit http://kartoza.com  to find out about open source:
> 
> Desktop GIS programming services
> Geospatial web development
> GIS Training
> Consulting Services
> 
> Skype: timlinux
> IRC: timlinux on #qgis at freenode.net 

—







Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux
IRC: timlinux on #qgis at freenode.net



signature.asc
Description: Message signed with OpenPGP
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] External providers in QGIS

[Tim Sutton]

Hi Rashad

Thanks so much for your email below….sometimes things are not always easy to 
figure out, especially as QGIS gets bigger and more complex. We will really 
value your contribution as we move forward … and we will try to come up with a 
solution that works well for everyone.

Best regards

Tim

> On 20 Feb 2018, at 13:09, Rashad Kanavath  wrote:
> 
> Hello,
> 
> Sorry for the misunderstanding about my last mail, I didn't want to
> be disrespectful. I would like to continue the discussion about this
> contribution.
> 
> We will push this contribution and try to answer to all
> questions, comments or issues about it. We will submit with my colleagues in
> few days the QEP to have a strong basis for the discussion about this PR.
> Thanks for setting up discussion on external providers at QGIS developer 
> meeting.
> I had also registered to this discussion in github page.
> I hope that we can continue to work together in a constructive spirit on this 
> issue.
> 
> --
> Thanks,
> Rashad
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

—







Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux
IRC: timlinux on #qgis at freenode.net



signature.asc
Description: Message signed with OpenPGP
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Future of Processing algs Help panel

[DelazJ]

Hi all,

Now that all the algorithms are documented in the User manual I'd like to
raise discussion on the status of the Help panel shown in algorithm dialog.
Depending on the algs (I'm here talking only about QGIS algorithms), we
have different status:
- provides an uptodate help
- provides a outdated description or a not really clear one (at least to
the non native speaker i am)
- no help panel.

I think this panel has to be there. It's a first good overview for the
user, allowing him/her to decide whether this alg could be pertinent or
not. If (s)he needs more details then the Help button for parameters
documentation is there. But it'd be better if it was available for all
algs, with an uptodate description (and it would help users with low
Internet, avoiding check in User manual).

This description is now written and available in Docs repo. What could be
the next step?

Regards,
Harrissou
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] [Qgis-psc] Call for possible vote on change to official plugin repo policy?

[Paolo Cavallini]

Il 21/02/2018 10:59, Tim Sutton ha scritto:

>> On 21 Feb 2018, at 09:01, Paolo Cavallini > > wrote:
>>
>> as plugin manager, I'd appreciate this enormously; I wish there was a
>> clear policy, with no room for interpretation. Having >= 1 ticket marked
>> as critical could be one, but this just moves decisions one step ahead.
>> Do you have a practic proposal?
> 
> 
> Can you clarify here if the ticket should be in QGIS tracker or in
> plugin repo tracker?

I confirm, I meant in the bugtracker of each individual plugin.

> What is to stop them just chasing the ticket state
> and then asking for a release?

This is exactly what I meant with "move decisions one step ahead".
Sorry for being unclear.

In short, what we need is a clear criterion for deprecation, with as
little subjectivity as possible. I would welcome any suggestion on this.

All the best.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis



signature.asc
Description: OpenPGP digital signature
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Changelog site upgrade

[Tim Sutton]

Hi All

NOTICE: ESPECIALLY FOR THOSE WORKING ON THE CHANGELOG AT THE HACKFEST...

We are going to push out some changes to the live changelog site this afternoon 
- the site will be unavailable (hopefully just for a few minutes) while I do 
the upgrade.

The upgrade will happen at 12h45 Madeira time, 14h45 South Africa time, 13h45 
CET time.

I will post another notice here when the upgrade is complete.

Regards

Tim


—







Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux
IRC: timlinux on #qgis at freenode.net



signature.asc
Description: Message signed with OpenPGP
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Recordings of Developer Meetup Sessions?

[Tim Sutton]

Hi Matt

> On 21 Feb 2018, at 02:59, Matt Kenny  wrote:
> 
> Hello -
> 
> I just saw a post from Tim Sutton regarding the Developer Meeting [1] 
> starting tomorrow. Will the sessions that have zoom meeting links be recorded 
> and made available to watch later?

Yes I do plan to record them and put them on YouTube if there are no hitches.

> 
> I am a daily user of QGIS and would love to figure out a way to contribute 
> back to the project.
> 
> Being able to watch the mentored sessions regarding setting up a development 
> environment, reporting/validating bugs, and writing tests would be exciting 
> to see.
> 
> Regardless, I hope that the event goes well this week!


Thanks for your email!

Regards

Tim

> 
> Thanks,
> Matt
> 
> [1]: https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018 
> 
> 
> m a t t h e w k e n n y
> @mattmakesmaps 
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

—







Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux
IRC: timlinux on #qgis at freenode.net



signature.asc
Description: Message signed with OpenPGP
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] [Qgis-psc] Call for possible vote on change to official plugin repo policy?

[Tim Sutton]

Hi

> On 21 Feb 2018, at 09:01, Paolo Cavallini  wrote:
> 
> Hi Nyall,
> 
> Il 21/02/2018 06:55, Nyall Dawson ha scritto:
>> On 19 February 2018 at 17:46, Paolo Cavallini  wrote:
> 
>>> I fully understand and support your concerns. Why not simply deprecating
>>> these plugin? I have adopted this approach (much too rarely, trying not
>>> to hurt authors too much) in the past, and I found it simple and
>>> effective. Once issues are fixed, I simply remove the `deprecated` flag,
>>> et voilà.
>>> Not sure we need a vote for this, just establishing sensible guidelines
>>> should be enough.
>> 
>> That sounds like a good technical solution.
> 
> so, we agree that simply deprecating a plugin is the way to go, right?
> 
>> But (like others have raised) I think we need a clear policy here so
>> that there's no misunderstanding or developers feeling like they're
>> "targeted". That's why I think we need a strong policy, voted in by
>> the voting community, so that there's NO chance that anyone can claim
>> that this is being abused.
> 
> as plugin manager, I'd appreciate this enormously; I wish there was a
> clear policy, with no room for interpretation. Having >= 1 ticket marked
> as critical could be one, but this just moves decisions one step ahead.
> Do you have a practic proposal?


Can you clarify here if the ticket should be in QGIS tracker or in plugin repo 
tracker? What is to stop them just chasing the ticket state and then asking for 
a release?

Regards

Tim


> 
>> What's the next step here? I'd very much like to see this continue
>> moving forward promptly.
> 
> IMHO we can agree on a solution without the need for a vote. In any
> case, I'm sure PSC could ratify any sensible decision that comes out of
> this discussion.
> 
> All the best.
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

—







Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux
IRC: timlinux on #qgis at freenode.net



signature.asc
Description: Message signed with OpenPGP
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Order of algorithms in processing

[Jakob Lanstorp]

@Borys, Yes this is what happens, thanks.

Jakob



-
Jakob Lanstorp
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer