Wiki !!!
by Johan Engelen
I need ours! :)
Thanks for fixing it,
Johan
11 years, 8 months
GSEAL issues (lots of them!)
by Alex Valavanis
Hi All,
I thought it would be worth mentioning that we need to get rid of all
direct access to private fields of objects as part of our GTK+ 3
migration.
i.e.
foo->bar = bar_val; // NO!!
gtk_foo_set_bar (foo, bar_val); //Yes!
bar_val = foo->bar; // NO!!
bar_val = gtk_foo_get_bar (foo); //Yes!
To check for these issues, you can compile inkscape with:
make CFLAGS+="-DGSEAL_ENABLE" CXXFLAGS+="-DGSEAL_ENABLE"
Note that there are probably hundreds of such problems, so any help
with the cleanup would be appreciated!
Usually there is a suitable GTK/GDK accessor function to fix the
problem. Sometimes (e.g. [1]) there isn't, which I guess implies that
we're doing something the "wrong" way.
Cheers,
Alex
[1] https://bugs.launchpad.net/inkscape/+bug/911174
11 years, 8 months
Bazaar advice
by Johan Engelen
Hi all,
A recent commit to lib2geom compressed almost all commits since februari
into one. Very annoying, although I know you can find out what those
individual commits were with some more clicking.
These mistakes don't surprise me; I am scared of the bzr tool that does
things I do not understand.
So to make people aware of the dangers of bzr, I'd like to give advice
to simple folks like me:
*************************************
I strongly advise you to not work in branches and merge it into trunk,
and stay away from any other so-called convenient advanced functionality
of bzr, like push-pull-whatever. Simply use it in 'svn mode'.
http://wiki.inkscape.org/wiki/index.php/Working_with_Bazaar#Using_a_centr...
*************************************
If you have fully understood how bzr works, perhaps you can try to use
the extra functionality. In that case, learn how to foul up the history
(like rev2000 in lib2geom) so you don't type in such commands.
Thank you very very very much,
Johan
(PS. no hard feelings to the committer of course! I blame the tool that
allows these things to happen)
11 years, 8 months
Canvas color option (Bug #169623)
by Nicolas Dufour
Hi all,
I've just committed a patch William Swanson did for the wishlist bug #169623 "Canvas color option" (https://bugs.launchpad.net/inkscape/+bug/169623). A rather popular wishlist (12 people declared being affected on LP). It compiles and works as expected on Windows XP and Ubuntu.
The canvas color is now set to the drawing background color (defined in the document properties), ignoring alpha. Thus if you choose a fully transparent black, the canvas will be black (instead of white as in the stable Inkscape version). Note that the modification doesn't affect exports (PNGs still use the alpha channel).
Don't hesitate to comment.
Regards,
--
Nicolas
PS: Apparently the snap indicator color is broken (it never gets the white stroke it has in the 0.48.x branch when using a dark background - SnapIndicator::set_new_snaptarget is *always* called with pre_snap=false), but it seems that the bug was already in the trunk (also reproduced on Windows XP with 10760, 10700, 10614 and 10568).
11 years, 8 months
