Forum: Inkscape bug?

I have this oddball behavior going on with copy/paste.  I am running 
0.47 on a mac with OS X Leopard.

I have a path that I am trying to copy and do "paste in place".  
However, when I paste the path, what I am getting is an IMAGE, not a 
path,  I can't edit it.  It has a white background, which shouldn't be 
there, and it doesn't paste in place.  It pastes off to the left of 
where it should be. I am wanting to paste it in place on a different 
layer, but even pasting it on the same layer creates an image, instead 
of a copy of the original path.

How I determined that it was an image was to go into the XML editor and 
watched what happened when I did the paste.  Sure enough, the XML editor 
states that the copy is an image, not a path.

What is going on?  Have I changed a setting somewhere by accident?  Or 
is this a bug?

Well...it's fixed, but I have no idea what was going on.  I trashed my 
install, and downloaded the .dmg from inkscape.org.  Ran it and did copy 
paste.  Still had the same issue.  Paste was an image, and I got a 
duplicate on my desktop.

So did a reboot.  Now everything seems to be working.  Very weird.

--- On Wed, 2/24/10, Elwin Estle <chrysalis_reborn@yahoo.com> wrote:

From: Elwin Estle <chrysalis_reborn@yahoo.com>
Subject: [Inkscape-user] bug?
To: inkscape-user@lists.sourceforge.net
Date: Wednesday, February 24, 2010, 9:38 AM

I have this oddball behavior going on with copy/paste.  I am running 
0.47 on a mac with OS X Leopard.

I have a path that I am trying to copy and do "paste in place".  
However, when I paste the path, what I am getting is an IMAGE, not a 
path,  I can't edit it.  It has a white background, which shouldn't be 
there, and it doesn't paste in place.  It pastes off to the left of 
where it should be. I am wanting to paste it in place on a different 
layer, but even pasting it on the same layer creates an image, instead 
of a copy of the original path.

How I determined that it was an image was to go into the XML editor and 
watched what happened when I did the paste.  Sure enough, the XML editor 
states that the copy is an image, not a path.

What is going on?  Have I changed a setting somewhere by accident?  Or 
is
 this a bug?




-----Inline Attachment Follows-----

On 24/2/10 15:38, Elwin Estle wrote:
> 
> How I determined that it was an image was to go into the XML editor and
> watched what happened when I did the paste.  Sure enough, the XML editor
> states that the copy is an image, not a path.
> 
> What is going on?  Have I changed a setting somewhere by accident?  Or
> is this a bug?

This is an issue with the pasteboard syncing feature between X11 and OS
X - please read the FAQ for a workaround:
"Copying and pasting in Inkscape creates pixellated images instead of
copying the vector objects "
<http://wiki.inkscape.org/wiki/index.php/FAQ#Copying_and_pasting_in_Inkscape_creates_pixellated_images_instead_of_copying_the_vector_objects>

hth, ~suv

On 24/2/10 15:38, Elwin Estle wrote:
> ... and it doesn't paste in place.  It pastes off to the left of
> where it should be. 

That's another setting to take care of with current X11 versions
installed by Apple on Leopard and Snow Leopard: in order to use the
'Alt' key for keyboard shortcuts you need to change the key mapping used
by X11 (else 'Alt' is ignored and you are simply pasting with 'Ctrl+V'
under the cursor instead of a 'Paste in Place')

You can
a) use the menu command 'Edit > Paste in Place'
b) change the X11 key mapping for one of the 'Option/Alt' keys as
described in the FAQ "How to make the Alt key work?"
<http://wiki.inkscape.org/wiki/index.php/FAQ#How_to_make_the_Alt_key_work_.3F>

~suv

On Feb 24, 2010, at 7:59 AM, ~suv wrote:

> 
> This is an issue with the pasteboard syncing feature between X11 and OS
> X - please read the FAQ for a workaround:
> "Copying and pasting in Inkscape creates pixellated images instead of
> copying the vector objects "
> <http://wiki.inkscape.org/wiki/index.php/FAQ#Copying_and_pasting_in_Inkscape_creates_pixellated_images_instead_of_copying_the_vector_objects>
> 
> hth, ~suv

There might be some complication due to a bit of random order being 
employed to choose which data flavors to offer and accept at which 
times. If you don have this continue, we could benefit from a quick 
check to see what types are being offered and passed through.

On 24/2/10 17:51, Jon Cruz wrote:
> check to see what types are being offered and passed through.
It always happens on Leopard (and Snow Leopard) - i.e. reproducible if
the X11 preferences are not changed.
Bug #307005 <https://bugs.launchpad.net/inkscape/+bug/307005>
“[OS X] copy & paste inserts a bitmap copy instead of the vector object”

On Snow Leopard, sometimes copy&paste completely fails, but the same
changes in the X11 preferences have been reported to bring back
copy&paste functionality within Inkscape:
Bug #460197 <https://bugs.launchpad.net/inkscape/+bug/460197>
“Can't copy objects in pre4, Snow Leopard”

Since the release of OS X 10.6 I have read several reports of 'GIMP on
OS X' users (osx port of GIMP [1]) that see the same clipboard failure
on Snow Leopard when copying&pasting within one instance of GIMP. They
tell that disabling that special X11 feature ("Update Pasteboard when
CLIPBOARD changes") helps to restore copy&paste within GIMP as well.

While it was never reported for Inkscape 0.46, this issue first was
noticed with Inkscape 0.46+devel *after* Apple updated its X11 to
version 2.1.6 (which is based on Xquartz 2.3.2 [2]) and confirmed by the
developer of Xquartz ("It is a known problem").

Could you explain with more details how to best monitor the data types
'offered and passed through' the clipboard of X11? I did once install
your clipboard utility 'dragndrop' [4], but was not succeeding at the
time to interpret any of the information it gave me on the content of
the clipboard [5].


~suv


[1] http://sourceforge.net/projects/gimponosx/
[2] http://xquartz.macosforge.org/trac/wiki/X112.3.2
[3]
http://thread.gmane.org/gmane.comp.graphics.inkscape.user/12363/focus=12365
[4] <http://sourceforge.net/projects/dragndrop/>
[5] http://article.gmane.org/gmane.comp.graphics.inkscape.user/12638