sikuli-driver team mailing list archive

[Ales Katona <almindor@xxxxxxxxx>]

The backtrace is:

[info] locale: en_US
Exception in thread "main" java.lang.NullPointerException
	at org.sikuli.ide.ImageButton.createFromString(ImageButton.java:241)
	at org.sikuli.ide.SikuliPane.replaceWithImage(SikuliPane.java:617)
	at org.sikuli.ide.SikuliPane.parseLine(SikuliPane.java:568)
	at org.sikuli.ide.SikuliPane.parseRange(SikuliPane.java:528)
	at org.sikuli.ide.SikuliPane.parse(SikuliPane.java:543)
	at org.sikuli.ide.SikuliPane.parse(SikuliPane.java:546)
	at org.sikuli.ide.SikuliPane.read(SikuliPane.java:427)
	at org.sikuli.ide.SikuliPane.loadFile(SikuliPane.java:372)
	at org.sikuli.ide.SikuliIDE.loadFile(SikuliIDE.java:838)
	at org.sikuli.ide.SikuliIDE.restoreSession(SikuliIDE.java:768)
	at org.sikuli.ide.SikuliIDE.<init>(SikuliIDE.java:713)
	at org.sikuli.ide.SikuliIDE.getInstance(SikuliIDE.java:138)
	at org.sikuli.ide.SikuliIDE.main(SikuliIDE.java:973)


This happens when I delete an image I use inside the sikuli code (not a sikuli region/capture). I use a path with my own captureScreen("path") (extension) function. The IDE crashes when the given path/image is not found it seems? I think the IDE tries to replace the path with the image from file and simply fails. For me it's not a problem atm. because I was just testing extensions and wanted to add a simple screenshotter function, but I guess these things can cause problems if people use some image paths in their scripts which are not related to the internal sikuli screenshot taker.

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

Title:
  sikuli start hangs after first try

Status in Sikuli:
  In Progress

Bug description:
  Sikuli version RC3, Linux x64 (Ubuntu 11.04)

  RC2 works fine, but in RC3 the IDE just doesn't start on subsequent
  tries. I open the IDE, load an existing script, run and quit. Then
  when I want to run the IDE again I get nothing. Running from command
  line just shows "[info] locale: en_US" and doesn't go anywhere from
  there.

  It's probably a locale related problem because in RC2 the line shows
  "sk_SK" (which is right) and just tells me no info for given locale.
  In RC3 it shows "en_US" (not right) and hangs.

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