TOPIC:

Ah, I forgot, the crashes on annotations where GetEditTextFormat should return nothing cause a signal 11 (segmentation fault) and happen as soon as I call GetEditTextFormat();

fixed, plz wait next version.

Hi,

tried out version 3.0beta6 and it fixes the crash issue.

However, I have 2 more issues.


First issue.

The invisible text issue seems to have resurfaced, with different behaviour than before.
Now it triggers if you:
1) edit a text field
2) exit and reenter the document
3) edit same the text field again
4) exit and reenter the document
==> The text field will show incomplete text. If you tap the field, in the edit box you will see the complete value and after editing it will look correct again. But as soon as you exit and reenter the document you will see incomplete text again.


Second issue.

I already wrote you about this one.

In my experience, tapping on a text field which already contains a value will crash the application with the exception at the bottom of this message (*).
You already dismissed this report as 'I cannot reproduce it', but I have more information for you.
I discovered it happens under a particular case.
As you probably know, EditText behaviour can be different on different devices, or different screen orientations on the same device, depending on screen height:
1) if enough space is present, keyboard will appear and editing will be performed inline within the EditText
2) if not enough space is present, a full screen editing widget will appear (with a done button on the right) and editing will take place there

This crash only happens in scenario 1.


Regards,
Michele


(*)
09-17 11:47:23.110 10113-10113/com.radaee.reader W/Siemens PDF﹕ OnAnnotClicked: Cogome2 ==> 20, 2
09-17 11:47:25.030 10113-10113/com.radaee.reader E/SpannableStringBuilder﹕ SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
09-17 11:47:25.030 10113-10113/com.radaee.reader E/SpannableStringBuilder﹕ SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
09-17 11:47:25.040 10113-10113/com.radaee.reader W/dalvikvm﹕ threadid=1: thread exiting with uncaught exception (group=0x41aca930)
09-17 11:47:25.050 10113-10113/com.radaee.reader E/AndroidRuntime﹕ FATAL EXCEPTION: main
android.view.WindowManager$BadTokenException: Unable to add window -- token android.view.ViewRootImpl$W@41ee07e8 is not valid; is your activity running?
at android.view.ViewRootImpl.setView(ViewRootImpl.java:567)
at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:246)
at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:69)
at android.widget.PopupWindow.invokePopup(PopupWindow.java:993)
at android.widget.PopupWindow.showAtLocation(PopupWindow.java:847)
at android.widget.PopupWindow.showAtLocation(PopupWindow.java:811)
at android.widget.Editor$PinnedPopupWindow.updatePosition(Editor.java:2312)
at android.widget.Editor$PinnedPopupWindow.show(Editor.java:2269)
at android.widget.Editor$SuggestionsPopupWindow.show(Editor.java:2511)
at android.widget.Editor.showSuggestions(Editor.java:1797)
at android.widget.Editor$1.run(Editor.java:1693)
at android.os.Handler.handleCallback(Handler.java:725)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5039)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
at dalvik.system.NativeStart.main(Native Method)

Here the culprit seems to not not the 'unable to add window' stacktrace, which I believe happened *after* the activity crashed, but the following 2 lines instead:

09-17 11:47:25.030 10113-10113/com.radaee.reader E/SpannableStringBuilder﹕ SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
09-17 11:47:25.030 10113-10113/com.radaee.reader E/SpannableStringBuilder﹕ SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length


Here is the verbose log surrounding this...

09-17 11:47:15.320 10113-10113/com.radaee.reader W/Siemens PDF﹕ OnAnnotClicked: Cogome2 ==> 20, 2
09-17 11:47:21.820 10113-10113/com.radaee.reader W/InputEventReceiver﹕ Attempted to finish an input event but the input event receiver has already been disposed.
09-17 11:47:21.820 10113-10113/com.radaee.reader W/InputEventReceiver﹕ Attempted to finish an input event but the input event receiver has already been disposed.
09-17 11:47:21.890 10113-10113/com.radaee.reader W/IInputConnectionWrapper﹕ beginBatchEdit on inactive InputConnection
09-17 11:47:21.890 10113-10113/com.radaee.reader W/IInputConnectionWrapper﹕ endBatchEdit on inactive InputConnection
09-17 11:47:23.110 10113-10113/com.radaee.reader W/Siemens PDF﹕ OnAnnotClicked: Cogome2 ==> 20, 2
09-17 11:47:25.030 10113-10113/com.radaee.reader E/SpannableStringBuilder﹕ SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
09-17 11:47:25.030 10113-10113/com.radaee.reader E/SpannableStringBuilder﹕ SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
09-17 11:47:25.040 10113-10113/com.radaee.reader D/AndroidRuntime﹕ Shutting down VM
09-17 11:47:25.040 10113-10113/com.radaee.reader W/dalvikvm﹕ threadid=1: thread exiting with uncaught exception (group=0x41aca930)
09-17 11:47:25.050 10113-10113/com.radaee.reader E/AndroidRuntime﹕ FATAL EXCEPTION: main
.......

Hi,

any news?

I can work around the crash issue (although I would really like it fixed), but I cannot work around the disappearing text one.
My application is mostly finished, but I cannot ship it to the customer with this bug present.

Let me recap it...

The invisible text issue seems to have resurfaced, with different behaviour than before.
Now it triggers if you:
1) edit a text field
2) exit and reenter the document
3) edit same the text field again
4) exit and reenter the document
==> The text field will show incomplete text. If you tap the field, in the edit box you will see the complete value and after editing it will look correct again. But as soon as you exit and reenter the document you will see incomplete text again.

Regards,
Michele

Hi,

sorry to bother you again, but since I'm getting no replies I'm starting to get worried.
I have invested a significant amount of time in building a product which is centred on you library, and almost all that is needed for my product to be ready is:
- you to fix the disappearing text bug
- me to purchase the library and perform final adaptations

My customer is starting to get insistent on release dates, but I cannot ship it until the disappearing text bug is fixed, as the whole product is based on editing PDF forms.

Regards,
Michele