sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

** Description changed:

+ ***** workaround for mentioned code-drag&drop problem
+ 
+ The mentioned problem only occurs, if the actions are done in the following sequence:
+ - Cut a piece of script 1 with an image in it 
+ (which is not referenced anywhere else in the script)
+ - Save the script 1
+ - Paste into the script 2
+ 
+ The IDE crashes with the cryptical error:
+ [error] Can't transfer: sun.awt.datatransfer.TransferableProxy@....
+ since the image is purged from script 1 when saving 
+ (it is no longer referenced in script 1)
+ 
+ if you do it this way:
+ - Cut a piece of script 1 with an image in it 
+ - Paste into the script 2
+ - Save the script 1
+ 
+ the problem does not occur.
+ 
+ -------------------------------------------------------------------
+ 
  This bug report is a follow up on
  https://bugs.launchpad.net/sikuli/+bug/1053438 as the main problem there
  has already been fixed.
  
  I think the deletion of the PNG images is way too rigorous. I would
  really like to see an option to turn off the automatic destruction of
  the referenced images.
  
  When I do the following action in the Sikuli editor:
  - Cut a piece of script with an image in it (which is not located anywhere else in the script)
  - Save the script
  - Paste the script
  
  I get the error:
  [error] Can't transfer: sun.awt.datatransfer.TransferableProxy@1a256c7
  
  And as RaiMan already said:
  "I just looked into the source - only 10 statements in try-catch block (unfortunately the error itself is not displayed :-(
  
  It is the part, where the images are copied from one .sikuli to the
  other."
  
  When there are any 'rogue'  PNG images in the directory (e.g. for future
  use) then these are also removed on save, as they are not referenced
  (yet)!
  
  I understand that cleaning up the Sikuli project directories can be a
  nice addition (although scripts shouldn't ever become too long). I'd
  rather invoke the clean-up manually or to have the option to save
  without doing a cleanup.
  
  On Sikuli r930, W7 SP1 64 bit

** Summary changed:

- X-1.0rc3: IDE: Removing not referenced images is too rigorous
+ X-1.0rc3: IDE: Removing not referenced images, when script is saved, is too rigorous

** Changed in: sikuli
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1054900

Title:
  X-1.0rc3: IDE: Removing not referenced images, when script is saved,
  is too rigorous

Status in Sikuli:
  New

Bug description:
  ***** workaround for mentioned code-drag&drop problem

  The mentioned problem only occurs, if the actions are done in the following sequence:
  - Cut a piece of script 1 with an image in it 
  (which is not referenced anywhere else in the script)
  - Save the script 1
  - Paste into the script 2

  The IDE crashes with the cryptical error:
  [error] Can't transfer: sun.awt.datatransfer.TransferableProxy@....
  since the image is purged from script 1 when saving 
  (it is no longer referenced in script 1)

  if you do it this way:
  - Cut a piece of script 1 with an image in it 
  - Paste into the script 2
  - Save the script 1

  the problem does not occur.

  -------------------------------------------------------------------

  This bug report is a follow up on
  https://bugs.launchpad.net/sikuli/+bug/1053438 as the main problem
  there has already been fixed.

  I think the deletion of the PNG images is way too rigorous. I would
  really like to see an option to turn off the automatic destruction of
  the referenced images.

  When I do the following action in the Sikuli editor:
  - Cut a piece of script with an image in it (which is not located anywhere else in the script)
  - Save the script
  - Paste the script

  I get the error:
  [error] Can't transfer: sun.awt.datatransfer.TransferableProxy@1a256c7

  And as RaiMan already said:
  "I just looked into the source - only 10 statements in try-catch block (unfortunately the error itself is not displayed :-(

  It is the part, where the images are copied from one .sikuli to the
  other."

  When there are any 'rogue'  PNG images in the directory (e.g. for
  future use) then these are also removed on save, as they are not
  referenced (yet)!

  I understand that cleaning up the Sikuli project directories can be a
  nice addition (although scripts shouldn't ever become too long). I'd
  rather invoke the clean-up manually or to have the option to save
  without doing a cleanup.

  On Sikuli r930, W7 SP1 64 bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1054900/+subscriptions