Hi there Bruce,
Try to make the SIGNAL signature match the C++ signature as that is what
PyQt will try to match. Specifically you are using Qt.MouseButton (the
Python version) when the C++ version would keep the '::'.
Try:
QObject.connect(self.emitPoint, SIGNAL("canvasClicked(QgsPoint &,\
Hi:
I am writing a python plugin to clip images to a user selected
rectangle and am stuck at the point where the plugin gets the
coordinates from mouse clicks. Here are some code snippets from my
plugin:
-
-
-
# connect QGSMapCanvas mouse click event to the rubb
Yes, I'm in the same case than Maning.
Agus
maning sambale wrote:
Documentation perhaps? I tried using
http://apps.sourceforge.net/trac/qgismetaedit/
But never, got past loading the example xmls, I am having difficulty editing.
I'm a newbie in metadata editing, normally I just create a simple
t
I plopped mine in the htdocs dir of OSGEO4W and it worked
After you log out of SourceForge or leave the project page for a length of time
the direct download links are forwarded to their HTML interface instead of a
direct download.
I am not sure if there is a way around this or not. I think
Tuesday 16 of June 2009 17:59:08 Sampson, David napisał(a):
>
> For the record, this is the error that is returned from qgis
>
> Error reading repository: Qgis Community plugin Repository
> Couldn't parse output from the repository
Hi, this error is a bit mysterious. If I open the file with Ka
For the record, this is the error that is returned from qgis
Error reading repository: Qgis Community plugin Repository
Couldn't parse output from the repository
Cheers
> -Original Message-
> From: qgis-user-boun...@lists.osgeo.org
> [mailto:qgis-user-boun...@lists.osgeo.org] On Beha
So I have posted a plugins.xml file that I thought might work base don
previous examples.
I double checked the version numbers and did have to make some changes
http://voxel.dl.sourceforge.net/sourceforge/qgiscommunitypl/plugins.xml
I tried using absolute links to the files residing in sorcefor
I don't want to speak on behalf of the community, I just came across what I
figured would work for the central repo and kinda matches typical; open source
projects that facilitate the three options.
Cheers
> -Original Message-
> From: qgis-user-boun...@lists.osgeo.org
> [mailto:qgis-
Tuesday 16 of June 2009 15:03:11 Sampson, David napisał(a):
>
> Just as I am going through a pseudo code exercise of release.py I see three
cases.
>
> 1. Current and previous stable versions VERSION
> 2. A Beta version is is being tested an on its way to stable. B
Tuesday 16 of June 2009 15:18:37 Sampson, David napisał(a):
>
> For a community plugin repo I assume that multiple authors might be involved
in the development of a plugin
>
> For the element... Someone
>
> Can this be a comman separated value.
sure
> I am thinking of automaticaly generating
For a community plugin repo I assume that multiple authors might be involved in
the development of a plugin
For the element... Someone
Can this be a comman separated value.
I am thinking of automaticaly generating this from an AUTHORS.txt file
Also, is there an e-mail optio we can add or wha
Just as I am going through a pseudo code exercise of release.py I see three
cases.
1. Current and previous stable versions VERSION
2. A Beta version is is being tested an on its way to stable. BETA
3. An unstable snapshot of the development trunk
Well, I assume that the two plugins I posted will remain in the wild as they
are designed from a tester's point of view and from an educational point of
view.
I would say that plugins that are general enough to benifit ,majority of QGIS
users make it to the core. For the other SPECIALIZED plu
Tuesday 16 of June 2009 08:47:06 Volkan Kepoglu napisał(a):
>
> it is very good opportunity to create two repos for the same plugin. One for
> stable and one for experimental purposes.
You can either create the two repos and recommend the unstable one only for
'experimenting' users, or put two p
Hi Agustin,
in your case, maybe the Geoinformatics article written by the current PSC
members for the QGIS 1.0 release in February this year can be used.
I added the link to the article on the wiki "Journals" page. It would be
great if more people can provide links to other articles about QGIS th
Hugentobler Marco wrote:
Hi Horst
I also like to have the node tools in a pull-down menu.
Still I think the separation basic editing toolbar / advanced editing toolbar
makes sense because some advanced tools are probably used less frequently, so
user should have the possibility to show/hide
I will use waht is provided in the web, but
I think that the best would be having the Quantum GIS Development Team
writing an article with a general description of QGIS basic
characteristics, history and
roadmap. Something equivalent to:
Anselin, Luc, Ibnu Syabri and Youngihn Kho (2006). GeoDa:
Title: Private Message from Bijay
Bijay P has sent you a private message Click to read messagePlease read it or Bijay will think you ignored this :( This message has been forwarded at the request of bijaykumar.m...@gmail.com. To block all emails from FanIQ, please click here.
On Tue, 16 Jun 2009 08:31:13 +0200
Otto Dassau wrote:
> Hi,
>
> On Mon, 15 Jun 2009 22:37:35 +0200
> Agustin Lobo wrote:
>
> > I'm a bit confused by the FAQ entry regarding
> > citation:
> >
> > "Quantum GIS Development Team (YEAR). GNU General Public License.
> > http://qgis.osgeo.org";
> >
19 matches
Mail list logo
