On Sat, Feb 2, 2013 at 9:22 AM, francescobocca...@libero.it <
francescobocca...@libero.it> wrote:
> fields = { 0 : QgsFields("ID", QVariant.Int),
> 1 : QgsFields("Area", QVariant.Double),
> 2 : QgsFields("Perim", QVariant.Double),
>
Le vendredi 01 février 2013 22:42:36, Martin Dobias a écrit :
> On Fri, Feb 1, 2013 at 9:11 AM, wrote:
> > Hi Martin,
> >
> > Good to see this plugin is getting some love !
> >
> > Le 2013-02-01 01:26, Martin Dobias a écrit :
> >> 2. instead of having a special provider, we could reuse an exist
Hi all,
i have a problem with new class QgsFields:
in my code i wrote:
fields = { 0 : QgsFields("ID", QVariant.Int),
1 : QgsFields("Area", QVariant.Double),
2 : QgsFields("Perim", QVariant.Double),
3 : QgsFields(field, QVa
On Fri, Feb 1, 2013 at 9:11 AM, wrote:
> Hi Martin,
>
> Good to see this plugin is getting some love !
>
> Le 2013-02-01 01:26, Martin Dobias a écrit :
>
>> 2. instead of having a special provider, we could reuse an existing
>> provider for viewing OSM layers - SpatiaLite seems to be the most
>>
On Fri, Feb 1, 2013 at 1:35 PM, Jürgen E. wrote:
> Hi Etienne,
>
> On Fri, 01. Feb 2013 at 13:01:35 -0200, Etienne Tourigny wrote:
>> Is there a way we can make this suggestion visible, other than adding
>> it to the api docs?
>
> There is now. Apparently since python 2.7 all deprecation warnings
Hi Etienne,
On Fri, 01. Feb 2013 at 13:01:35 -0200, Etienne Tourigny wrote:
> Is there a way we can make this suggestion visible, other than adding
> it to the api docs?
There is now. Apparently since python 2.7 all deprecation warnings where
disabled by default. The messages now appear in the
On Fri, Feb 1, 2013 at 12:40 PM, Angus Carr wrote:
> Hi,
>
> I am a plugin developer who was bitten by this API change. It's easily
> worked around with a try...except... structure, but that becomes unneeded
> clutter. I am working on a plugin that I want to work in the future API and
> the stable
On Fri, Feb 1, 2013 at 12:40 PM, Angus Carr wrote:
> Hi,
>
> I am a plugin developer who was bitten by this API change. It's easily
> worked around with a try...except... structure, but that becomes unneeded
> clutter. I am working on a plugin that I want to work in the future API and
> the stable
Hi,
I am a plugin developer who was bitten by this API change. It's easily
worked around with a try...except... structure, but that becomes unneeded
clutter. I am working on a plugin that I want to work in the future API and
the stable API at version 1.8, so right now I need that clutter to make i
Hi everybody,
I'm pleased to announce that I've pushed the current state of dual-view
to github [1]
Anybody interested in having a look at it is kindly requested to do so
and share his thoughts concerning the development.
Anybody who does not want or can't compile the branch can easily have
Hi Robert,
I also created a standalone version of the filter symbol [1][2] but I'm
not yet happy with it. It looks a bit "blocky" to me. Maybe the lighter
part of the background is too intensive?
I also thought, that for the expression combined with something else,
the "something else" part
Hi All,
I am looking for some example implementation of setEditType in QGIS python
plugins. The enums that do not need any additional information is just fine.
However, it is unclear when it comes to enums like ValueMap, EditRange,
CheckBox etc., I want to use strings 'true' or 'false' for chec
hi list,
A friend of mlne warned me about the need to patch the rails engine for
security reasons. I have not checked further, as I no longer run a redmine
instance on my server, but I think it is safer to have a look for the Qgis
redmine server ?
http://news.techworld.com/security/3418412/ruby-o
Hi Martin,
Good to see this plugin is getting some love !
Le 2013-02-01 01:26, Martin Dobias a écrit :
2. instead of having a special provider, we could reuse an existing
provider for viewing OSM layers - SpatiaLite seems to be the most
viable candidate. Once data is imported from XML into a da
14 matches
Mail list logo