On 05/03/2012 01:49 PM, Marco Hugentobler wrote:
Hi
There is also a ticket about a regression in the print composer: since
1.7.x there is an issue when printing large formats on win32
I've just tried to print to A0 with QGIS 1.6 on win7 (64bit, but QGIS
compiled on WoW 32 bit) and got the
Il 14/05/2012 21:22, Giovanni Manghi ha scritto:
http://hub.qgis.org/projects/quantum-gis/issues?query_id=23
I recently spotted another bug that caused a crash but Alex promptly
fixed it. So far then the above 3 tickets are still the confirmed
regressions. Other things are surfacing but all
I agree it is a bit worrying. It would be nice to see them done so we
can cut 1.8 loose
and move on with the clean up for 2.0.
If you think a bit of publicity is what is needed I'm happy to write a
quick blog
post, throw something up on twitter, facebook and Google+.
- Nathan
On Tue, May 15,
Hi
On Tue, May 15, 2012 at 1:41 PM, Nathan Woodrow madman...@gmail.com wrote:
I agree it is a bit worrying. It would be nice to see them done so we
can cut 1.8 loose
and move on with the clean up for 2.0.
If you think a bit of publicity is what is needed I'm happy to write a
quick blog
Hi devs,
I was wondering what is the current status of 1.8 release. I have a
number of new features I would like to create pull requests for, but I
guess it is better to wait until 1.8 release before that.
Etienne
On Fri, May 4, 2012 at 8:26 AM, Marco Hugentobler
Hi Etienne,
On Mon, 2012-05-14 at 16:17 -0300, Etienne Tourigny wrote:
Hi devs,
I was wondering what is the current status of 1.8 release. I have a
number of new features I would like to create pull requests for, but I
guess it is better to wait until 1.8 release before that.
Hi Marco,
I've just tried to print to A0 with QGIS 1.6 on win7 (64bit, but QGIS
compiled on WoW 32 bit) and got the crash. For me, it looks like a
memory problem, not like a regression.
-QGIS on win7 compiled with msvc 64 bit: printing to A0 works
-Linux 64bit: printing to A0 works (I
Hi Tim
Perhaps Giovanni, it would be good also to do that 'weekly blockers'
post to the dev list to bring the key issues to the lists attention?
yes, as discussed in Lyon I will do that. Meanwhile I already removed
the blocker tag to the printing issue and I believe that ticket about
licence
ok, then can we close the ticket? What about also adding a warning when
a user on win tries to print a large format?
Agreed, it is reasonable to add a warning for win32 (though I need to
make a few experiments to figure out the pixel limit that works).
Regards,
Marco
Am 04.05.2012 11:46,
Hi
On Wed, May 2, 2012 at 11:09 PM, Giovanni Manghi
giovanni.man...@faunalia.pt wrote:
On Thu, 2012-05-03 at 07:00 +1000, Nathan Woodrow wrote:
For me http://hub.qgis.org/issues/5327 has needs to be fixed before
the release. In it's current state it renders editing polylines and
polygons
Hi
There is also a ticket about a regression in the print composer: since
1.7.x there is an issue when printing large formats on win32
I've just tried to print to A0 with QGIS 1.6 on win7 (64bit, but QGIS
compiled on WoW 32 bit) and got the crash. For me, it looks like a
memory problem, not
Hi all.
I see that there are 5 issues marked as Blocker: how are we going to
deal with them? What is the date currently expected for release?
All the best, and thanks.
--
Paolo Cavallini
See: http://www.faunalia.it/pc
___
Qgis-developer mailing list
For me http://hub.qgis.org/issues/5327 has needs to be fixed before the
release. In it's current state it renders editing polylines and
polygons useless and frustrating. This would not be good such a otherwise
good release.
- Nathan
On Wed, May 2, 2012 at 7:08 PM, Paolo Cavallini
On Thu, 2012-05-03 at 07:00 +1000, Nathan Woodrow wrote:
For me http://hub.qgis.org/issues/5327 has needs to be fixed before
the release. In it's current state it renders editing polylines and
polygons useless and frustrating. This would not be good such a
otherwise good release.
the issues
Hi all.
I think we should take seriously the 80 current blocking issues
http://trac.osgeo.org/qgis/query?status=assignedstatus=newstatus=reopenedmust_fix=Yesorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=componentmilestone=Version+1.7.0report=16
My suggestion is to
Hi,
Thanks for the link!
I started working on this. I will not remove the Must fix tag on my
own, but already corrected priorities (incorrectly put as critical when
in fact there is no crash nor data loss).
I'm working mainly on stuff related to vector (and its symbology, legend
and printing).
16 matches
Mail list logo
