Since Processing has been mentioned a couple of times in the thread, just
some clarification:
- Processing can create memory layers, but only for native algorithms (that
is, not from SAGA, GRASS, etc). The option is available in the button aside
the text box where the destination path is entered
-
Forwarded to list
Forwarded Message
Subject:Re: [Qgis-developer] Memory Layers - some proposals
Date: Thu, 25 Sep 2014 06:04:19 -0800
From: Gary Sherman
Organization: GeoApt LLC
To: Matthias Kuhn
CC: gsher...@geoapt.com
On 9/25/14 1:10 AM, Matthias Ku
Hi,
I have some not so good news for all who arrive on wednesday and before
thursday late afternoon. I was just informed by the linuxhotel, that
they will have another big event on thursday, 2nd october. They have given
priority to this event, because that's what they make money with (we only
pay
About the python dependencies, I propose to share a list of dependencies of
the plugin, where everyone can add and propose those necessary to its
plugin.
This list could then be taken into consideration during the release of the
new version of QGIS, which may already contain them.
For example, I
On 25 September 2014 00:32, Luca Manganelli wrote:
> Hi, (i'm using qgis 2.4)
>
> how can view the object properties of a composer item I added with my plugin?
> I tried with showItemOptions(...) but it doesn't work
>
> in this example, I add a composerMap, but I cannot find a way on how
> to auto
On Wed, Sep 24, 2014 at 4:32 PM, Luca Manganelli wrote:
> [CUT ALL]
> # these commands doesn't show the item properties
> composerView.selectedItemChanged.emit(composerMap) # doesn't work
> composer.showItemOptions ( composerMap ) # doesn't work
I found a way to do this programmatically. The two
Aren't there two different possibilities in which such layers can be used:
* As a scratch layer for the user, which he may want to save in the end
* As a means for plugins to show information to the user
In the first scenario, the user may actually want to save the
information because he real
How to verify if the signal « feature added » is emitted from an add feature
tool?
De : qgis-developer-boun...@lists.osgeo.org
[mailto:qgis-developer-boun...@lists.osgeo.org] De la part de Nejia
Envoyé : mercredi 24 septembre 2014 16:09
À : qgis-developer@lists.osgeo.org
Objet : [Qgis-developer
On Thu, Sep 25, 2014 at 04:03:04PM +1000, Nathan Woodrow wrote:
> What about a icon in the legend to note that it it's not going to be saved?
I like the icon idea, but would still additionally have a warning
at save time.
I see those "temporary" layers like "drafts". That is, something you do
not
Hey all,
I think the best course of action here is to hold off until after 2.6 so we
can review this thing as a whole solution rather then rushing it in last
minute and then moving the target later.
IMO we could in the future use sqlite in memory datastore for the memory
provider which gives us a
On Thu, Sep 25, 2014 at 09:02:07AM +0700, Mathieu Pellerin wrote:
> Regarding the saving aspect of it, IMO it needs to be worked out. I've had
> a couple of users over here already reporting "data loss" with the
> following scenario:
> 1. Open his/her project
> 2. Copies one polygon from a large da
ur of:
* edit node tool
* move feature
* rotate feature
* move label
* rotate label
* any other press-pan-release map tool that I am not aware of
???
Best wishes,
Denis
__ Information from ESET Mail Security, version of virus signature
database 10461 (20140925) __
The
Hi,
this topic already was discussed recently, see this thread
http://osgeo-org.1560.x6.nabble.com/Processing-i18n-support-td5155677.html
In short, Processing has i18n support, but some code parts still miss it. We
are working on this, but patches are welcome.
2014-09-25 9:56 GMT+03:00 Arnaud M
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
__ Information from ESET Mail Security, version of virus signature
database 10461 (20140925) __
The message was checked by ESET Mail Security.
http://www.ese
I agree.
It seem me a silly question.
If an user choose a memory layer it know that is a memory layer
:)
So it is not a permanent dataset.
I like the memory layer because they as really useful for temporary
elaborations and quickly tests.
lso another question is.
If an user choose the memory lay
Hi,
Please excuse my ignorance, but
Why would you want a memory (as in RAM) layer when you want permanent data?
For portability reasons?
That's fine, but then we should offer a possibility to support
portability support for a real geo-format (with spatial index and all
the goodies). To stuff
On 25/09/2014 4:51 pm, "Mathieu Pellerin" wrote:
>
> Re Temporary Layers, I find it slightly better than Scratch Layer for non
native English speakers (i.e. more to the point in "simple" English :) ).
>
What happens when we port the memory layer saver to core though? Temporary
layers are no long
17 matches
Mail list logo
