Hi Fred,
did you change anything in the last time internally? I'm now having a lot of problems, that I never had. I didn't check a lot of 2.5/2.6/3.0b1-3 because of the compile problems. But now as I can compile with 3.0b4, I recognized that serious problems come fast on Android and iOS app, and slower on web. I checked back with 3.0b3 in web and had same problems, but with 2.6beta it seems to work as with 2.40.
from a canvas gadget I normally by click open a windowdialog to select one of 4 actions, but after working a bit the windowdialog no longer opens, but one action is directly started
some windowdialogs open, but there are gadgets simply missing after some use
some windowdialogs open, but are simply missing the data in the gadgets and shown buttons don't react
Looks to me as if there are some memory problems, crashed vars or whatever, I'm using the old windows and gadgets style that I've used now for years, but sometimes with own html dom style changes.
Greets, hoerbie
Last edited by hoerbie on Sat Jun 15, 2024 5:14 pm, edited 1 time in total.
I need more info/code. We changed Cordova version in 2.50 so it could be that, but memory problem shouldn't appear in js, as all is garbages. May be you can monitor the memory on windows if you feel it getting slower
You can may be try in release mode (disable the debugger)
Hi,
thanks for asking and sorry, as I could now debug some of the problems, it looks like it is not serious, so I changed the subject.
At first I was really shocked how bad the app worked or not worked when using longer, but:
When dialogs were not fully opened or filled with content, there were some gadget-ids used in DisableGadget(), ClearGadgetItems() etc., that only in some configurations are used and in other configuration simply are not defined, and then it crashed.
So this comes from the new code checks and debugger, although it is my interest to have a better stable app, I think there will be a lot of additional work to check every part of the app for such things
When my action select dialog was not used and direct an action was called, there seem to be changes on the Android compile at #PB_EventType_LeftButtonDown and #PB_EventType_LeftButtonUp and #PB_EventType_LeftClick.
Until now I've set the object for the action at "Down" event and called the action select dialog on "Up" event, when there was no big difference in the touch points, because there can additionally be some other actions from "Down"->"Move"->"Up".
But after "Down" and "Up" now seems to come the "Click" event (faster or changed order?), that only on Android now direct selects the action button that in the select dialog will be at the same mouse position, where before the dialog the object was selected by touch, and Android is so fast, that the dialog doesn't show up.
Will have to think longer, how to solve all use cases here.
Other things I couldn't debug until now, but I think there will be more problems due to the new code checks.
Will do more checks now in the browser, where warnings/errors are shown.
