Fatal signal 11 with beta 2.50

Informatix

Expert
Licensed User
Longtime User
Hello,

I have reports from my customers about your new version 2.50 (beta). When they use my UltimateListView product with it, they get a Fatal signal 11 (SIGSEGV), i.e. a violent crash. Some examples work, some others don't. Since my product doesn't use any special memory trick or system hack, and works fine with B4A v2.30, it seems there's a bug in your new version. Unfortunately, I don't have the new version (and for obvious reasons with beta versions, I prefer to not install it), so I cannot help a lot. I can provide you with logs sent by users. Here's one of them (unfiltered).
If you have no clue about this, I will install a virtual box on my computer to test the new version.
 

Attachments

  • ulv21b4a2501.txt
    13.4 KB · Views: 288

Informatix

Expert
Licensed User
Longtime User

It's what I call a bug: when something does not work as expected and we have to use a workaround. For http://www.b4x.com/forum/bugs-wishlist/23846-bringtofront-image-not-working.html#post138023, why don't you suggest instead to call the invalidate method of the container (panel or activity holding the view) to refresh the children display ? I'm pretty sure that will solve the problem.
 

Informatix

Expert
Licensed User
Longtime User
Invalidate will not help in that case (if I remember correctly).

It's not the view method that must be called, but its parent method (in an activity, call the activity.invalidate, in a panel, call the panel.invalidate). It's a case I encountered for other reasons and that's related to JellyBean. I just tried it and that solved the issue (in an activity and in a panel).
 

thedesolatesoul

Expert
Licensed User
Longtime User
No. If you use B4A v2.3 you have to use the library version 1.2. If you use B4A v2.5, you have to use the library version 1.25.
I'm going to send a link to the new library to everyone.
Does this mean all libraries have to be re-compiled for B4A 2.50?
Or those that reference the B4A Class in a specific way?
 
Cookies are required to use this site. You must accept them to continue using the site. Learn more…