Erel,
I think you understood all the way around. It runs faster in debug mode than in release mode. That's the wierd thing
-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
CustomListView - A flexible list based on ScrollView
- Thread starter Erel
- Start date
- Similar Threads Similar Threads
- Status
I think you understood all the way around. It runs faster in debug mode than in release mode. That's the wierd thing
[V. 1.70]
I would add (um... I added to my version) GetDividerHeight (property or function).
Also, I think that an exception handler for an "index out of bound" error should be added to:
otherwise the app will crash.
I would add (um... I added to my version) GetDividerHeight (property or function).
Also, I think that an exception handler for an "index out of bound" error should be added to:
B4X:
'Returns the Panel stored at the specified index.
Public Sub GetPanel(Index As Int) As Panel
Dim p As Panel
p = panels.Get(Index) 'this is the parent panel
Return p.GetView(0)
End Sub
This is the desired result if you try to access an invalid index. If the developer would like for some reason to catch this error instead of fixing the code then it can be added in the developer's code.
This is an important concept. Library developers (CLV is a library in this regard) should avoid catching exceptions whenever possible. This is the developer responsibility to decide how to handle errors.
In this case it is a programming error so it is even more clear. If a developer tried to get an invalid panel then the code should help him fix this error. Returning a different panel (maybe the last one) will lead to other errors which will be more difficult to debug.
In this case it is a programming error so it is even more clear. If a developer tried to get an invalid panel then the code should help him fix this error. Returning a different panel (maybe the last one) will lead to other errors which will be more difficult to debug.
Without that error you would not get the correct result and not know why you dont get it. I agree with erel. The whole idea is not just to have an app without any crashes you want to have an app that does what you programmed it to do! Then u need to catch all errors and fix them.
494 posts about CLV and this is not the right place to talk about it?
Its not related to CLV, its related to coding in general.
This was not my intention, my was a suggestion about the CLV.
I see many similarities between an "internal" array and any exceptions and elements of the CLV.
I also have some doubts about the dividerHeight: what do I do, hang and suit?
P.S. I don't know how to translate "taccio e mi adeguo?" (used google translate but I don't trust much this translation
)
That's true. This is why it is good that an out of bounds error is raised when the developer tries to access an invalid panel.
I think I've lost the thread, because it's exactly the message that you get:
java.lang.IndexOutOfBoundsException: Invalid index 500, size is 5
I would certainly have forgotten what my question was (two days for me are too many
).- Status