At this point, as long as I have a work around that means I don't need
to redo my entire week-long illustration, I'm cool. :)
At least when I go to the librsvg list this time, I'll have definite
answers to give them. :) Thanks guys!
On 6/20/05, bulia byak <buliabyak@...> wrote:
> On 6/20/05, mental@... <mental@...> wrote:
> > I'm not sure what the best workaround is yet, or whether it's worth
> > doing (versus getting librsvg to fix their code *sigh*). Bulia?
>=20
> Remembering the amount of effort it took us to code the visibility
> management which is both valid and works the way we want, I'd say
> forget it. Everyone must fix their own bugs; it's not a bug of ours.
>=20
> --
> bulia byak
> Inkscape. Draw Freely.
> http://www.inkscape.org
>

On 6/20/05, mental@... <mental@...> wrote:
> Would you mind filing a bug against librsvg in gnome bugzilla?
The original reporter: will you please do it?=20
--=20
bulia byak
Inkscape. Draw Freely.
http://www.inkscape.org

Quoting bulia byak <buliabyak@...>:
> Remembering the amount of effort it took us to code the
> visibility management which is both valid and works the way we
want,
> I'd say forget it. Everyone must fix their own bugs; it's not a
bug
> of ours.
Would you mind filing a bug against librsvg in gnome bugzilla?
-mental

On 6/20/05, mental@... <mental@...> wrote:
> I'm not sure what the best workaround is yet, or whether it's worth
> doing (versus getting librsvg to fix their code *sigh*). Bulia?
Remembering the amount of effort it took us to code the visibility
management which is both valid and works the way we want, I'd say
forget it. Everyone must fix their own bugs; it's not a bug of ours.
--=20
bulia byak
Inkscape. Draw Freely.
http://www.inkscape.org

Found the problem.
librsvg doesn't like visibility:visible
If you go into the XML editor, and remove ";visibility:visible" from
that path's style attribute, it should begin showing up in GIMP etc.
Since visibility:visible is legal (see
http://www.w3.org/TR/SVG/painting.html#VisibilityProperty), this
indicates a bug in librsvg (which most GNOME apps use for rendering
SVG, GIMP included).
I'm not sure what the best workaround is yet, or whether it's worth
doing (versus getting librsvg to fix their code *sigh*). Bulia?
-mental

On 6/20/05, linux peach <linuxpeach@...> wrote:
> I can copy and paste into an drawing just fine, I simply can't
> copy-cut-paste an object that's already in the drawing.
My advice is, don't concentrate on copy/paste. If you really want to
do the job of librsvg developers for them, try to analyze the SVG
code. Eliminate the differences between the files one by one until you
find the minimal change that triggers it.
--=20
bulia byak
Inkscape. Draw Freely.
http://www.inkscape.org

Ok, gnome-fs-directory is the original file.
I opened the file, selected the light front object of the folder,
copied it, cut it, and pasted it back in as if I had never even
touched it. I saved the file as -ccp.
The front object I copied-cut-pasted has disappeared from all views in
gnome/gimp/nautilus except inkscape.
On 6/20/05, linux peach <linuxpeach@...> wrote:
> I only changed the one object in the -issue file, but ok.
> =20
> Oh wait, no, there isn't a problem copying and pasting in an image from
> another source, there is only the problem of taking an object inside of a
> current drawing copying it, cutting it, and pasting it back into the same
> illustration.
> =20
> I can copy and paste into an drawing just fine, I simply can't
> copy-cut-paste an object that's already in the drawing.
>=20
> On 6/20/05, mental@... <mental@...> wrote:
> > Quoting linux peach <linuxpeach@...>:
> >=20
> > > Any and all objects that are copy-cut-pasted.
> >=20
> > I can't replicate this, and there are too many changes between the=20
> > first two documents you sent for me to be able to tell which change
> > might be the problem.
> >=20
> > Try this:
> >=20
> > 1. take a document that looks OK in gimp, saved with the version of
> > Inkcape you are testing with=20
> >=20
> > 2. copy and paste an object in it, making no other changes
> >=20
> > 3. save the result as another document
> >=20
> > 4. see if the copy-and-pasted object disappears in gimp
> >=20
> > 5. if so, send us both documents
> >=20
> > if not we can look into other causes
> >=20
> > -mental
> >=20
>=20
>

I only changed the one object in the -issue file, but ok.
Oh wait, no, there isn't a problem copying and pasting in an image from=20
another source, there is only the problem of taking an object inside of a=
=20
current drawing copying it, cutting it, and pasting it back into the same=
=20
illustration.
I can copy and paste into an drawing just fine, I simply can't=20
copy-cut-paste an object that's already in the drawing.
On 6/20/05, mental@... <mental@...> wrote:
>=20
> Quoting linux peach <linuxpeach@...>:
>=20
> > Any and all objects that are copy-cut-pasted.
>=20
> I can't replicate this, and there are too many changes between the
> first two documents you sent for me to be able to tell which change
> might be the problem.
>=20
> Try this:
>=20
> 1. take a document that looks OK in gimp, saved with the version of
> Inkcape you are testing with
>=20
> 2. copy and paste an object in it, making no other changes
>=20
> 3. save the result as another document
>=20
> 4. see if the copy-and-pasted object disappears in gimp
>=20
> 5. if so, send us both documents
>=20
> if not we can look into other causes
>=20
> -mental
>

Quoting linux peach <linuxpeach@...>:
> Any and all objects that are copy-cut-pasted.
I can't replicate this, and there are too many changes between the
first two documents you sent for me to be able to tell which change
might be the problem.
Try this:
1. take a document that looks OK in gimp, saved with the version of
Inkcape you are testing with
2. copy and paste an object in it, making no other changes
3. save the result as another document
4. see if the copy-and-pasted object disappears in gimp
5. if so, send us both documents
if not we can look into other causes
-mental

Any and all objects that are copy-cut-pasted.
On 6/20/05, mental@... <mental@...> wrote:
>=20
> Quoting linux peach <linuxpeach@...>:
>=20
> > I can change gradients, I can do anything and everything inside
> > of inkscape without a single issue, *except* copy-cut-paste. The
> > instant I use those three commands to an object that's already in
> > the file, that object disappears in gnome/nautilus/gimp/gtk/etc.
>=20
> Does this also happen for objects that don't have gradients? Or
> just objects with gradients?
>=20
> -mental
>

Quoting linux peach <linuxpeach@...>:
> I can change gradients, I can do anything and everything inside
> of inkscape without a single issue, *except* copy-cut-paste. The
> instant I use those three commands to an object that's already in
> the file, that object disappears in gnome/nautilus/gimp/gtk/etc.
Does this also happen for objects that don't have gradients? Or
just objects with gradients?
-mental

Ok. I'm on .40 in Ubuntu.
When I look at the -issue file, or if I use it as an actual icon, rect337
is missing, completely from all views within gnome. When I open inkscape,
rect337 appears just fine. The result of using the icon in gnome/nautilus
et al is that I do not see that one object at all in the icon. So if I go
to correct the icon in inkscape, the object is already there and visible.
I can change gradients, I can do anything and everything inside of inkscape=
=20
without a single issue, *except* copy-cut-paste. The instant I use those=20
three commands to an object that's already in the file, that object=20
disappears in gnome/nautilus/gimp/gtk/etc.=20
On 6/19/05, bulia byak <buliabyak@...> wrote:
>=20
> On 6/20/05, linux peach <linuxpeach@...> wrote:
> > I have included two sample files: the original gnome-fs-directory.svgfi=
le,
> > and then the modified gnome-fs-directory-issue.svg file that has a majo=
r
> > object that has been copied-cut-pasted, that no longer appears visible.
>=20
> Both files contain 7 objects. Of these 7, one is a group of 0 objects
> and is therefore invisible and unselectable (except by Ctrl+A) - in
> both files. The only difference is that in -issue, two of the paths
> are distorted by node-editing and have different z-order. There's no
> other difference between the files.
>=20
> Both files display the same in Batik/Adobe as in Inkscape.
>=20
> So, can you explain what exactly is missing, and why you are sure it's
> still there? And which version of Inkscape?
>=20
> --
> bulia byak
> Inkscape. Draw Freely.
> http://www.inkscape.org
>

Yeah, gimp shows it ncorrectly as well.
On 6/20/05, mental@... <mental@...> wrote:
>=20
> Quoting bulia byak <buliabyak@...>:
>=20
> > Both files contain 7 objects. Of these 7, one is a group of 0
> > objects and is therefore invisible and unselectable (except by
> > Ctrl+A) - in both files. The only difference is that in -issue,
> > two of the paths are distorted by node-editing and have different
> > z-order. There's no other difference between the files.
> >
> > Both files display the same in Batik/Adobe as in Inkscape.
>=20
> Have you checked in something using librsvg (e.g. gimp)? I suspect
> we might be seeing another rendering bug in librsvg...
>=20
> -mental
>

Quoting bulia byak <buliabyak@...>:
> Both files contain 7 objects. Of these 7, one is a group of 0
> objects and is therefore invisible and unselectable (except by
> Ctrl+A) - in both files. The only difference is that in -issue,
> two of the paths are distorted by node-editing and have different
> z-order. There's no other difference between the files.
>
> Both files display the same in Batik/Adobe as in Inkscape.
Have you checked in something using librsvg (e.g. gimp)? I suspect
we might be seeing another rendering bug in librsvg...
-mental

Quoting bulia byak <buliabyak@...>:
> Mental: I have a vague memory of you writing the code to supply
> namespace declarations based on prefixes used. If I remembered
> this correctly, can you please fix that code to never include a
> declaration for xml: prefix?
Please file a bug so I don't forget. I'm pulled in a lot of
directions these days.
-mental

Quoting bulia byak <buliabyak@...>:
> On 6/20/05, aaron@... <aaron@...> wrote:
> > I'm starting to think the failure with PyXML isn't because of
> the "xml:"
> > prefix but rather because of the "xmlns:xml" declaration
> itself.
>
> Wow! I did not notice that Inkscape inserts xmlns:xml itself. I
> was absolutely sure we can't do such a foolish thing :)
Whoops. Ow. My bug.
I thought I'd remembered to take care of that and omit 'xml' from
the list of namespace bindings emitted in repr-io...
-mental

Wolfram Quester wrote:
> On Mon, Jun 20, 2005 at 06:43:13AM -0500, aaron@... wrote:
>>Bryce Harrington wrote:
>>In CVS this can be done from the Misc tab in the Inkscape Preferences
>>dialog.
>
> I have the problem with the effects menu too. (debian unstable, cvs last
> week). I deleted .inkscape in my homedir and had a look in the dialog
> you mention but I don't see any possibility to enable the menu there
> (see attached screenshot). I also have problems with 3 extensions, but I
> don't know yet if I should configure --with-python --with-perl to get
> them working. I update from cvs atm an will recompile soon.
> The affacted extensions are:
>
> Extension "Blur Edge" failed to load because a dependency was not met.
> Dependency::
> type: plugin
> location: path
> string: bluredge
>
> Extension "GIMP Gradients" failed to load because a dependency was not met.
> Dependency::
> type: plugin
> location: path
> string: gimpgrad
>
> Extension "Grid" failed to load because a dependency was not met.
> Dependency::
> type: plugin
> location: path
> string: grid
Yeah, the effects menu checkbox in the preferences dialog is pretty new.
I think it was added Friday or Saturday.
You do not need to configure with python or perl. But I don't know what
you need to do to get those plugins working. I think I remember Ted
saying he was going to disable plugins for a while while he
rearchitectured things. I was hoping that he would fill us in when he
gets back.
If you do get it to work please record your steps on the wiki:
http://inkscape.org/cgi-bin/wiki.pl?GettingEffectsWorking
Aaron Spike

Hi alltogether,
On Mon, Jun 20, 2005 at 06:43:13AM -0500, aaron@... wrote:
> Bryce Harrington wrote:
> >On Thu, Jun 09, 2005 at 08:10:56PM +0200, Lucas Vieites wrote:
> >> I still don't have the "Effects" menu
> >> Am I missing some step here?
> >
> >You also need to turn on the menu in your preferences.xml file. ;-)
>
> In CVS this can be done from the Misc tab in the Inkscape Preferences
> dialog.
I have the problem with the effects menu too. (debian unstable, cvs last
week). I deleted .inkscape in my homedir and had a look in the dialog
you mention but I don't see any possibility to enable the menu there
(see attached screenshot). I also have problems with 3 extensions, but I
don't know yet if I should configure --with-python --with-perl to get
them working. I update from cvs atm an will recompile soon.
The affacted extensions are:
Extension "Blur Edge" failed to load because a dependency was not met.
Dependency::
type: plugin
location: path
string: bluredge
Extension "GIMP Gradients" failed to load because a dependency was not met.
Dependency::
type: plugin
location: path
string: gimpgrad
Extension "Grid" failed to load because a dependency was not met.
Dependency::
type: plugin
location: path
string: grid
Thanks,
Wolfi
>
> Aaron Spike

Bryce Harrington wrote:
> On Thu, Jun 09, 2005 at 08:10:56PM +0200, Lucas Vieites wrote:
>> I still don't have the "Effects" menu
>> Am I missing some step here?
>
> You also need to turn on the menu in your preferences.xml file. ;-)
In CVS this can be done from the Misc tab in the Inkscape Preferences
dialog.
Aaron Spike

On 6/20/05, linux peach <linuxpeach@...> wrote:
> I have included two sample files: the original gnome-fs-directory.svg fi=
le,
> and then the modified gnome-fs-directory-issue.svg file that has a major
> object that has been copied-cut-pasted, that no longer appears visible.
Both files contain 7 objects. Of these 7, one is a group of 0 objects
and is therefore invisible and unselectable (except by Ctrl+A) - in
both files. The only difference is that in -issue, two of the paths
are distorted by node-editing and have different z-order. There's no
other difference between the files.
Both files display the same in Batik/Adobe as in Inkscape.
So, can you explain what exactly is missing, and why you are sure it's
still there? And which version of Inkscape?
--=20
bulia byak
Inkscape. Draw Freely.
http://www.inkscape.org