My project is a daily planner app, and I'm having trouble with the When List.AfterPicking function
When I select something on my list I get a runtime error saying the values "error" and "0" are coming from
The string "error" is a string I put in to flag it, but I am unaware as to where the "0" is coming from.
I need to delete a certain event (the one the user selects from the list) from the list - in a to do list fashion, but I can only do this by selecting something from the list.
I am working on the yellow function at the very bottom of the picture - a .aia is also attached for your convenience.
What is the other side? The left side of the block? You could display the result for example in a label... or use an if statement... loads if possibilities...
Perhaps it would be of mutual benefit to better explain the program. This is a daily planner app, in which there is a text box, timepicker, and datepicker to create an event. The data is compiled into a string (the AddEvent procedure), which is added to a tinyDB, which in turn goes into a list. The contents of this list are shown with the ListView element. I have created the when List AfterPicking function to delete an event on the list, this event is the event that has been clicked.
That is the purpose of this function, but what it currently does is displays a runtime error, a brief message stating that the values "Events" and "0" are not acceptable arguments. I have replaced "Events" with "error" as to flag it for you to easily see. In the runtime error now, if you run the program on an emulator, the "Events" is replaced by "error", proving that that is the first unacceptable argument. There is also a variable that sets itself to whatever the selection index is on the listView.
I assume the way to fix this error is to replace these two statements with ones that the program can accept. My questions are:
What do I replace the string that currently says "error" with?
Where does this "0" value from the runtime error come from?
What can I do to fix this "0" value once it has been identified.
Your code does seem to have an error in the fundamental creation of an event, one that I can't begin to comprehend. This is the new runtime error that I receive when I write an event title and click create event.