On Jan 9, 2011, at 7:38 AM, ~suv wrote:

I don't think it would be too late for the win32 packages of 0.48.1 (they are not yet done), though it doesn't leave any time to test the updated cairo version on Windows (if cairo 1.10.2 can be built without issues on Windows ;) ).

@Michael - could you do the same for the osx packages of 0.48.1? On modevia, the most recent devel builds still list cairo 1.10.0 as included dependency.

We definitely want to look at however much testing as we can. Windows, especially, gives us some of the worst problems in terms of bugs and support.

We also need to avoid setting *requirements* of Inkscape up until enough distros have brought it into mainline, LTS, etc.

But windows and mac might be good.

On 10/01/2011, at 2:38 AM, ~suv wrote:

On 9/1/11 16:12, J.B.C.Engelen@...1578... wrote:

...

Cairo 1.10.2 has been released, and a bug concerning Inkscape was fixed. https://bugs.launchpad.net/inkscape/+bug/665628 It is a pity it is just too late to include in 0.48.1

@Michael - could you do the same for the osx packages of 0.48.1? On modevia, the most recent devel builds still list cairo 1.10.0 as included dependency.

No problems, I've updated cairo to 1.10.2. Nightly builds for Mac OS X from tomorrow will use it.

Cheers, Michael

De : Krzysztof Kosiński <tweenk.pl@...400...>

I have updated cairo, I'm waiting for a rebuild of Inkscape after updating the trunk to commit it - there's a required change in build.xml because the upstream Cairo win32 build started using libpng14, and Inkscape and GTK loaders are still using libpng12.

I've just noticed a small regression on Windows XP, Inkscape revision 10006, devlibs r21 (clean build): moving the mouse cursor on the layers list in the layers dialog (you must have at least 2 layers) makes the show and lock icons disappear. Not reproduced with revision 9997, devlibs r20.

Regards. -- Nicolas

I can reproduce the disappearing in the filter settings dialog. All inputs are invisible if i drag the mous over it.

Maybe we shoud use the older cairo/pixman version to publish 0.48.1 and fix this annoying error in 0.48.2 ?

Sincerely,

UweSch

Am 21.01.2011 15:53, schrieb Nicolas Dufour:

...

I've just noticed a small regression on Windows XP, Inkscape revision 10006, devlibs r21 (clean build): moving the mouse cursor on the layers list in the layers dialog (you must have at least 2 layers) makes the show and lock icons disappear. Not reproduced with revision 9997, devlibs r20.

Also affected:

• Filters editor dialog (filters inputs are completely invisible).
• Undo history (flickering icons).
• Font editor (strange black strip).

Other lists that don't use icons (in the Preferences and Properties dialogs) are not affected. -- Nicolas

---

Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Ausgehende eMail ist virenfrei. Von AVG Free SB überprüft - www.avg.de Version: 9.0.872 / Virendatenbank: 271.1.1/3402 - Ausgabedatum: 01/25/11 08:34:00

2011/1/25 ~suv <suv-sf@...58...>:

... or release 0.48.1-1 for Windows with the previous cairo version (1.8.8) and an updated win32 package 0.48.1-2 with cairo 1.10.2 as soon as a fix is available?

The older releases have a PDF export bug for black strokes, which might be more severe han an UI glitch. What do you think? It's easy to revert the Cairo upgrade temporarily, or the person building the Windows installer could use an earlier revision of devlibs.

Regards, Krzysztof

Hello,

Sorry for the late reply.

De : ~suv <suv-sf@...58...> Any comments from Windows users (Johan, JazzyNico, Uwesch,...)? The issue is limited to the Windows builds afaict [1] and its impact on usability seems difficult to evaluate without actually using an affected build.

I'm afraid we're going to have the same kind of reaction we had with the persistent markers with 0.48 on GNU/Linux. The problem with UI issues is that even when they are not severe (here it's just flickering, and doesn't prevent Inkscape from working), they are more visible than PDF export bugs. Frankly (if it's not too late), I'd rather keep the old devlibs for 0.48.1 and start using the new one (and try to find a fix or a workaround) in 0.48.2.

Regards. -- Nicolas

On Mon, Feb 7, 2011 at 2:52 AM, ~suv <suv-sf@...58...> wrote:

On 7/2/11 11:36, Nicolas Dufour wrote:

...

...

De : ~suv <suv-sf@...58...> Any comments from Windows users (Johan,  JazzyNico, Uwesch,...)? The issue is limited to the Windows builds afaict [1]  and its impact on usability seems difficult to evaluate without actually  using an affected build.

I'm afraid we're going to have the same kind of reaction we had with the persistent markers with 0.48 on GNU/Linux. The problem with UI issues is that even when they are not severe (here it's just flickering, and doesn't prevent Inkscape from working), they are more visible than PDF export bugs. Frankly (if it's not too late), I'd rather keep the old devlibs for 0.48.1 and start using the new one (and try to find a fix or a workaround) in 0.48.2.

As far as I know, the 0.48.1-1 packages already uploaded to sf.net (installer, archives, debug and portable) have been built with the current devlibs (cairo 1.10.2).

Not sure, but it looks like we'll have to bear with the user reactions until the next bug-fix release is ready (0.48.2). Or replace the uploaded files with new packages (0.48.1-2), built with the old devlibs (cairo 1.8.8). The links to the new files have already been spread quickly via twitter et al. - replacing the files now could cause some confusion for users. OTOH the release wasn't yet officially announced.

I see minimal harm with what has spread via twitter that is not official. :) If people file bug reports about it prior to official announcement and say they found out via AwesomeSoftware2011 on twitter, we just need to tell them to watch trusted people (myself, joncruz, prokoudine, or any number of others) for *accurate* information about releases. Confused users that trust third-party sources instead of trusted/official sources are the least of my worries and imho kinda deserve the pain they subject themselves to (like people who get malware infected machines because they pirate via P2P and such).

Enough of that mini-rant. :) I think that we should see about repackaging the win32 versions with the less "annoying" bug for now until fixed libs are released. Uwe & Chris, do you think you'll be able to do that? BTW, has anyone checked if it's a known issue upstream?

Cheers, Josh

W dniu 16 stycznia 2011 01:51 użytkownik Krzysztof Kosiński <tweenk.pl@...400...> napisał:

I still don't see

Oops. Continuing, I don't see 0.48.1 being available for download yet, so maybe the new Cairo can make it after all. I think we are suffering from high bus factor again. [1] Is the release process documented somewhere so that someone other than Ted can do it? Regards, Krzysztof

[1] http://en.wikipedia.org/wiki/Bus_factor