Hi Miro,
Do you use the current master/trunk version? Your wish nr 2 is already
implemented in the current master. For each side you can set if you want
to label the grid or not and whether you want to label it horizontally
or vertically.
Your first wish isn't implemented yet, but I agree th
I believe it should be not very hard to implement and very nice to have:
1. In Print Composer / Map item / Grid tab add option "Tick"
- there are two options (Solid and Cross) which is great. But it would be
great to have third option "tick" which would do only ticks on border -
basically the Cros
On Sat, Jan 5, 2013 at 7:48 PM, Andreas Neumann wrote:
> Hi,
>
> See my reply inline.
>
>>> Where do you get the list of properties from? Could tags and descriptive
>>> text be added to these settings?
>>
>> Actually they are read from the settings file / registry by QSettings.
>> So anything not
Sure, why don't you upload what you think it should look like. I will start
working on this tonight and poke around to see just how difficult this is
to get working.
Thanks,
~Ben
On Sun, Jan 6, 2013 at 4:25 PM, Nathan Woodrow wrote:
> Hey Ben,
>
> I think a multi frame feature is inevitable in
On Sat, Jan 5, 2013 at 7:48 PM, Andreas Neumann wrote:
> Hi,
>
> See my reply inline.
>
>>> Where do you get the list of properties from? Could tags and descriptive
>>> text be added to these settings?
>>
>> Actually they are read from the settings file / registry by QSettings.
>> So anything not
Hey Ben,
I think a multi frame feature is inevitable in QGIS and is something that I
have always wanted to have. I think we can take the idea of Data Frames
that ArcGIS has and expand on areas that we don't like.
Having higher level groups, which would be the frames, would work fine and
having j
On Thu, Jan 3, 2013 at 10:37 AM, Matthias Kuhn wrote:
> I've just been able to segfault:
>
> a = dataProvider.getFeatures( QgsFeatureRequest().setFilterFid( featureId )
> )
> a.rewind()
> a.next()
Hi Matthias
I was able to replicate the problem in postgres provider - I have
fixed the issues, ple
So I found a few related bugs to what I wanted to do so I don't know if
this is incorporated already.
http://hub.qgis.org/issues/2348
http://hub.qgis.org/issues/4846
with the second link being what I think I am going for with one substantial
difference. I want to have a main map of a section of s
On Sun, 6 Jan 2013 04:43:10 -0800 (PST)
Régis Haubourg wrote:
> Maybe we should ask what is the global roadmap for vector menu tools. Most
> of actions in the menu are part of ftools. Do we start replacing them one by
> one by C++ core actions, or do we have a global plan to rebuild thoses
> acti
OK for starting specifications. A good start could be a Arcgis - QGIS
comparison to find missing features. I really like small graphics to help
user understand what the tool is doing. I put that on my list. If you
already have proposals, let's post drafts here, and then finalise in a
redmine ticket
Hi,
Sorry for top-posting. I switched the main Options dialog over to
vertical tabs. Couple of features:
* Long labels should wrap, but may not look great at 3 lines. Seems to
be a bit of an issue when using a custom font, where the wrapping
doesn't work quite the same as with the Qt default font
On Sun, Jan 6, 2013 at 8:20 PM, Andreas Neumann wrote:
> In my opinion it also should be a core tool in QGIS, not a plugin. These
> spatial queries are really core GIS functions, not optional extensions.
>
I agree this one of the reasons that I brought up the topic of moving code
plugins to core
Am 06.01.2013 11:09, schrieb Régis Haubourg:
> Hi Andreas,
> +1 for me.
> Tolerance threshold should be square units ( area) for polygon - polygons
> intersects, and simple units (length) for line-polygon intersections.
yes
> Beyond that, I had in mind to fund a GUI and performance evolutio
Hi Benedict,
As Giovanni said - an overview map element (which seems to be what you
describe) is already there in QGIS master - not in version 1.8.
Multiple views in one QGIS project would be very nice to have - I
wouldn't call it data frames - just because ESRI calls them data frames
- we should
Hi Andreas,
+1 for me.
Tolerance threshold should be square units ( area) for polygon - polygons
intersects, and simple units (length) for line-polygon intersections.
Beyond that, I had in mind to fund a GUI and performance evolution of
spatial query tool. It is not very fast, and user inter
Hi Benedict,
I really would like to have one day data frames too. It would really
simplify multimap composers and label tuning for paper dedicated maps.
In current state, user has to play with 'lock layer' option and switch from
mapcanvas to mapcomposer a lot of times to finalize a good map compo
Hi all,
I have created a new MapTool(c++) for rotating multiple selected
features interactively using mouse
movement(https://github.com/qgis/Quantum-GIS/pull/376).
Normal Usage:
Select features on map.
Press mouse and drag to rotate about the selected features'
bounding-box's center.
Advan
17 matches
Mail list logo
