Hey Denis,
There is a 4th option of course and that is a key modifier for override to
do click-click. I was planning on doing that a while ago when I thought
about the same thing.
So adding something like shift+click to enabled click-click mode.
Not sure if that is better but there is not a
What about a icon in the legend to note that it it's not going to be saved?
- Nathan
On Thu, Sep 25, 2014 at 3:57 PM, Mathieu Pellerin nirvn.a...@gmail.com
wrote:
Thoughts:
- I don't think warning should be occurring when creating a memory layer
(that is when pasting as new layer, when
On 25/09/2014 4:03 pm, Nathan Woodrow madman...@gmail.com wrote:
What about a icon in the legend to note that it it's not going to be
saved?
I like that idea - I'd imagine if memory/scratch layers always displayed
the RAM icon in the legend and not the layer symbol then it would be a
permanent
Possibly although that'd clutter that space. Renaming Memory Layers to
Temporary Layers would also give a good clue.
That said, I must say I quite enjoy using the memory layer saver, I'd be
sad to see this function not making it into core.
Martin raised an important issue re format. What about
On 25.09.2014 08:02, Nathan Woodrow wrote:
Hey Denis,
There is a 4th option of course and that is a key modifier for
override to do click-click. I was planning on doing that a while ago
when I thought about the same thing.
So adding something like shift+click to enabled click-click mode.
On 25/09/2014 4:27 pm, Mathieu Pellerin nirvn.a...@gmail.com wrote:
Possibly although that'd clutter that space.
Not really- it could be handled in the same way as the editing icon is at
the moment. That doesn't take up any extra room as it replaces the style
swatch.
That said, I must say I
Personally I like the memory layer and use it frequently.
The icon idea sounds good to me. Ideally it could be a RAM icon combined
with the type of geometry (Point, Line, Polygon).
I also like the idea of having the memory layer as a core feature - but
then there should be a user-friendly way to
I guess the main issue with replacing the style swatch is we loose that for
a ram icon that will be there all the time so you can't see the style set
on the layer.
Personally I do prefer the name Temporary rather then Memory.
- Nathan
On Thu, Sep 25, 2014 at 4:38 PM, Nyall Dawson
Hi,
I think we should be open-minded towards Denis ideas and not
categorically reject any changes in curent behaviour. Enabling the CAD
mode enables a lot of possibilities compared to the current mode.
I am not a CAD expert either, but I am often impressed about how
efficiently my Autocad
As a name, I like Scratch layer or Temporary layer. I see that
people can confuse Memory with permant storage.
Andreas
Am 25.09.2014 06:41, schrieb Nathan Woodrow:
I guess the main issue with replacing the style swatch is we loose that
for a ram icon that will be there all the time so you
Nyall, I don't think there's a compatibility issue with memory layers.
Those are by their nature QGIS-dependant data, the same way ArcGIS can't
simply open a .qgs project file, a .qml layer properties file, etc.
One of the nice feature of memory layers (and its sister plugin memory
layer saver)
Hi,
It would be wonderful if someone could work on preserving formatting and
add comment support for the expressions in the QGIS 2.7 dev phase.
I can try and help to find some funding, if a dev is interested in
implementing this and can provide a quote.
Andreas
Am 24.09.2014 19:44, schrieb
What about to translate the processing plugin ?
There is no doubt that processing is more powerfull/modular than the old
ftools, but users who don't speek english find that the processing
module and its toolbox is less accessible than former fTools menu.
Content to translate will be :
-
On 25/09/2014 4:51 pm, Mathieu Pellerin nirvn.a...@gmail.com 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
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
-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.eset.com
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
of
???
Best wishes,
Denis
__ Information from ESET Mail Security, version of virus signature
database 10461 (20140925) __
The message was checked by ESET Mail Security.
http://www.eset.com
___
Qgis-developer mailing list
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 dataset
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
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
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 :
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
On Wed, Sep 24, 2014 at 4:32 PM, Luca Manganelli luc...@gmail.com 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
On 25 September 2014 00:32, Luca Manganelli luc...@gmail.com 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
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
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
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 gsher...@geoapt.com
Organization: GeoApt LLC
To: Matthias Kuhn matthias.k...@gmx.ch
CC:
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
29 matches
Mail list logo
