Hi all,
There is somehow an inconsistency in the behaviour of the current
editing map tools.
Some, like add features, uses the left click to trigger the action.
Others, like the node tool or move feature use press-pan-release mouse
events:
* mouse press to select the node/feature
* mouse
Luca, I just followed your advice and moved the Processing.initialize()
call to initGUI().
I did not test, however, to check that startup time has improved. The
change is already in master, so you can test it.
Let me know if you have more suggestions
Thanks!
2014-09-19 14:02 GMT+02:00 Luca
Hi all,
moving Processing initialization to initGui() does not change situation.
I played with this about week or two ago. The problem is in another
place and I plan to work on this with Victor at hackfest
2014-09-24 12:10 GMT+03:00 Victor Olaya vola...@gmail.com:
Luca, I just followed your
Great. Thanks for the work Alex.
Looking forward to being at the HackFest!
2014-09-24 11:15 GMT+02:00 Alexander Bruy alexander.b...@gmail.com:
Hi all,
moving Processing initialization to initGui() does not change situation.
I played with this about week or two ago. The problem is in another
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all.
Concerning http://hub.qgis.org/issues/11260 , I'm unsure this is not
the intended behaviour. Any opinion?
All the best.
- --
Paolo Cavallini - www.faunalia.eu
QGIS PostGIS courses: http://www.faunalia.eu/training.html
-BEGIN PGP
On 24/09/2014, at 16:56 , Denis Rouzaud wrote:
Hi all,
There is somehow an inconsistency in the behaviour of the current editing map
tools.
Some, like add features, uses the left click to trigger the action.
Others, like the node tool or move feature use press-pan-release mouse events:
On 24-09-14 10:56, Denis Rouzaud wrote:
So, the bottom line, any objection to changing the behaviour 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
???
Hi Denis,
though I'm not a hard core
Hi Ramon,
On 24.09.2014 13:23, Ramon Andiñach wrote:
On 24/09/2014, at 16:56 , Denis Rouzaud wrote:
Hi all,
There is somehow an inconsistency in the behaviour of the current editing map
tools.
Some, like add features, uses the left click to trigger the action.
Others, like the node tool
On 24.09.2014 13:23, Ramon Andiñach wrote:
I further suspect that since the node tool does more than just move
nodes, this is probably asking for a separation into node-move and a
node-insert and a segment-move and a... tools. I really like having
all of these in one tool, instead of
Hi Richard,
On 24.09.2014 14:00, Richard Duivenvoorde wrote:
On 24-09-14 10:56, Denis Rouzaud wrote:
So, the bottom line, any objection to changing the behaviour of:
* edit node tool
* move feature
* rotate feature
* move label
* rotate label
* any other press-pan-release map tool that I am
as you make it more consistent and usable: go
:-)
That's the idea. Or at least the goal ;)
Cheers,
Denis
__ Information from ESET Mail Security, version of virus signature
database 10458 (20140924) __
The message was checked by ESET Mail Security.
http://www.eset.com
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 automatically view the properties in the Composer Window:
# open
Just implemented it for text edit (when using QgsFilterLineEdit or
QLineEdit). [1]
Please let me know if it works and if you are missing it in other places
as well.
Matthias
[1]
https://github.com/qgis/QGIS/commit/3f8a860503c78689c981234f874771f8b1277c97
On 24.09.2014 16:59, Matthias Kuhn
Hi,
I have a plugin that allows to change an attribute value of added feature to
the selected value of a combo-box.
I change the attribute when the signal featureAdded is emmited (ie. Before
the endEditCommand of add feature is called) so in this undo command we
have in the order:
1-
It would be nice to use setSpecialValueText for spin boxes if possible
too ;)
Adding a clear button could be done similarly to the the QgsDateTimeEdit.
Cheers,
Denis
On 24.09.2014 17:13, Matthias Kuhn wrote:
Just implemented it for text edit (when using QgsFilterLineEdit or
QLineEdit). [1]
Thank you Matthias for the very quick fix.
This fix only changes the NULL value behavior of the widget - right?
This will probably have no effect on what QGIS server does with NULL
values, right?
Thanks a lot,
Andreas
Am 24.09.2014 15:13, schrieb Matthias Kuhn:
Just implemented it for text
What about writing per tool, the behaviour you propose in a QEP
(https://github.com/qgis/QGIS-Enhancement-Proposals) so we can discuss
it there?
yeah, I wonder if this really needs one. It's quite a small change with
not many consequences.
I think the mails so far already show that it's no
Il 23/09/2014 19:23, Alex Mandel ha scritto:
I'll also note that several people have had success using pip
within OSGeo4w. See previous posts on qgis and osgeo4w lists.
Making pip easier to use in OSGeo4w is likely a better choice.
+1 After finding the correct documentation page, it was
Hi Andreas
On Wed, Sep 17, 2014 at 10:56 PM, Andreas Neumann a.neum...@carto.net wrote:
I noticed that line breaks are not preserved. This makes the statement
much harder to read.
Is there a chance that future QGIS versions could preserve linebreaks or
is there a problem saving and
Hi Andreas
On 24.09.2014 17:55, Andreas Neumann wrote:
Thank you Matthias for the very quick fix.
This fix only changes the NULL value behavior of the widget - right?
This will probably have no effect on what QGIS server does with NULL
values, right?
Correct, it's just representation on
Hi Martin
On 24.09.2014 19:32, Martin Dobias wrote:
Hi Andreas
On Wed, Sep 17, 2014 at 10:56 PM, Andreas Neumann a.neum...@carto.net wrote:
I noticed that line breaks are not preserved. This makes the statement
much harder to read.
Is there a chance that future QGIS versions could
Hi Alex
On Wed, Sep 24, 2014 at 12:23 AM, Alex Mandel
tech_...@wildintellect.com wrote:
Several of us on IRC have discussed this topic in depth before, at least
in regards to external python deps. My leaning is to just wrap pip
functionality to help users.
Indeed - it would be really nice if
Hi all,
The recent discussion around memory layers in another thread has started me
thinking about the best way to expose them more readily to users.
As such, I've opened a pull request which ports Borys Jurgiel's New Memory
Layer plugin to core (PR #1591). Hopefully this can be merged for 2.6.
Hi Nyall
On Thu, Sep 25, 2014 at 3:31 AM, Nyall Dawson nyall.daw...@gmail.com wrote:
Hi all,
The recent discussion around memory layers in another thread has started me
thinking about the best way to expose them more readily to users.
As such, I've opened a pull request which ports Borys
On 24/09/2014, at 21:52 , Bernhard Ströbl wrote:
Bottom line:
1) Intuitive is what you are used to.
This admittedly is true.
2) The way it currently works in QGIS is IMHO more intuitive because I am
used to it :) and it is the way graphic software works (I tried
LibreOfficeDraw, Inkscape
On 25/09/2014, at 01:00 , Anita Graser wrote:
What about writing per tool, the behaviour you propose in a QEP
(https://github.com/qgis/QGIS-Enhancement-Proposals) so we can discuss
it there?
yeah, I wonder if this really needs one. It's quite a small change with
not many consequences.
On 25 Sep 2014, at 6:01, Ramon Andiñach cust...@westnet.com.au wrote:
I am not saying the idea is bad but the consequences might be larger than
you expect especially for occasional users if the behaviour of the tools is
different from what they would expect from their prior experience (of
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 and pastes is as a new memory
layer (very useful feature introduced in
On 25.09.2014 04:02, 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 and pastes is as a
Hi Ramon,
Thanks for having a look. I downloaded a trial of MI yesterday but
couldn't launch it due to licence issues (!?).
On 25.09.2014 03:01, Ramon Andiñach wrote:
On 25 Sep 2014, at 6:01, Ramon Andiñach cust...@westnet.com.au wrote:
I am not saying the idea is bad but the consequences
Hi all,
I'll try to summarize.
*QEP*: I don't mind doing one, but I think it's a bit early since we are
still discussing.
*Problematic*: Drag'n'drop map tools prevent from enhancing CAD tools in
QGIS. For this, it is *required *to add click-click to all map tools.
*Other softwares:*
CAD
Thoughts:
- I don't think warning should be occurring when creating a memory layer
(that is when pasting as new layer, when adding the result of a processing
algorithm as memory layer, or creating a blank memory layer)
- I don't think the user should be able to disable the warning message
(which
32 matches
Mail list logo
