There should be an engineering requirement that requires putting any changes on those two meme buttons, then judging the facial expression below BEFORE implementation.
I keep running into this issue with my cross-platform macOS and iOS app. It’s extremely frustrating that I can’t share a simple timer class between the two projects. Feedback:
And clearly someone once just decided to have it just to be as-is … probably because “it may break code”… I’d rather have 1 version break some event name than keeping my mind pointing the wrong way because someone ever deciced to have 2 different events on differen platforms for the same class !!
I just hope Xojo for once decides to be consistent like in ALL ways.
I agree and it’s annoying to have to cater for two commands in my code to perform the same thing, but remember that this thinking is what gave us API 2 (< prepare for arrows>which I love </prepare for arrows >).
The timer issue is an example where I subclass the Xojo timer class and create my own methods/functions with appropriate names consistent for all platforms. I’ve done this for most of the UI classes now because with a large app over 10 years old it was a quicker fix than attempting to search/replace every instance in the source code with a new syntax every time Xojo decides to have a brain fart.
Problem fixed.
Agreed I don’t really understand why the need for all the desktop framework prefixes when this could (should) have been fixed by the IDE picking the appropriate code merely by defining the target platform.
As for the “new features”… made my own set classes ages ago, and ZIP functionality was written way back in the REALBasic days - from memory thanks to either either Thomas Templeman or Kem Tekinay