search

dexapier / android-scripting

Automatically exported from code.google.com/p/android-scripting
0 stars 0 forks source link

NullPointerException when editing in SL4A editor with "Auto-close" enabled with third-party script. #616

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
(Using SL4A Scheme from http://code.google.com/p/sl4a-scheme/)
1. Open a .scm script in the SL4A default editor.
2. Ensure that the SL4A preference for Enable Auto-close is checked.
3. Back in the editor, modify the script contents (even adding a line break).
Note: navigating through the script with the arrow keys works correctly.

What is the expected output? What do you see instead?
A modified version of the script.  Instead, SL4A force closes.

What version of the product are you using? On what operating system?
SL4A r5x05 on Android 2.3.4

Please provide any additional information below.
Digging through the source code, it appears that the problem lies in that there 
is no corresponding Language implementation (for scheme, in this case), and of 
course no entry in the SupportedLanguages.KnownLanguages enum.

(I had originally reported this on the sl4a-scheme project, before digging far 
enough through the stacktrace and source code to see where it originated.)

Please see the attached stacktrace for exact details.

Original issue reported on code.google.com by matthewc...@gmail.com on 25 Mar 2012 at 4:19

Attachments:

GoogleCodeExporter commented 9 years ago 
Fixed in latest r5x (http://www.mithril.com.au/android/sl4a_r5x.apk) (5x06)

Original comment by rjmatthews62 on 25 Mar 2012 at 10:58

GoogleCodeExporter commented 9 years ago

Original comment by rjmatthews62 on 25 Mar 2012 at 11:06

GoogleCodeExporter commented 9 years ago 
Thanks for the quick turnaround -- I really appreciate it!  Unfortunately, it 
doesn't seem to have fixed it - still the same problem, with the same 
stacktrace in the logs (or, at least the NPE occurs in the same place - 
ScriptEditor.java, line 411).  I double checked -- the version string in the 
upper right of the SL4A window *does* say r5x06.

Perhaps it didn't build completely/correctly, and just the version string was 
updated?

Original comment by matthewc...@gmail.com on 26 Mar 2012 at 4:10

GoogleCodeExporter commented 9 years ago 
Just so there's a "paper trail" on the issue log, I'm confirming that a later 
build (r5x07) posted to the google group fixed this issue.

Thanks!

Original comment by matthewc...@gmail.com on 27 Mar 2012 at 4:13