sikuli-driver team mailing list archive

[sgfit <1579812@xxxxxxxxxxxxxxxxxx>]

I think I found how to fix it in my case, but not the ultimate cause.

When I saved a new screenshot from sikuliide, the resulting file was
saved as a 0-byte file.  Attempting to save or open the .sikuli from
then on caused the 'read returned null' error mentioned before.

I haven't tracked down why the screenshot was saved as a 0-byte file,
but if this error comes up for anyone else, that's probably the cause.

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

Title:
  [1.1.0] IDE: problems when saving scripts with many lines and then
  with startup restore

Status in Sikuli:
  In Progress

Bug description:
  Sikuli 1.1.0, Windows 7 x64.

  When attempting to save a .sikuli in the IDE, instead of saving, the
  contents of the .sikuli folder are deleted and the IDE returns the
  error message "[error] EditorPane: read returned null".  The contents
  of the previous .sikuli script are still present in a tab labelled
  'Untitled'.

  When attempting to save the tab labelled untitled, the IDE returns this error message, and the .sikuli folder is not generated:
  "[error] EditorPane: read returned null"

  Restarting the IDE then returns:
  "[error] EditorPane: read returned null"
  "[error] IDE: restoreScriptFromSession: Can't load: C:\Users\username\Documents\Sikuli\project\win7.sikuli"

  Permissions for the folders in question allow reading and writing, so
  doubt it is a file permissions issue.

  Steps to reproduce:
  1. Create a large script (>200 images, >1000 lines)
  2. Attempt to save.

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