Seven or eight years ago, there were a few threads about this error message, encountered when trying to port working Mac apps to iOS. I also recall from that period the opinion that “people who do not understand subclasses have no business using RealBasic.” The combination of the two has me in a bad place.
I have a (very) large desktop app implemented entirely with methods. No subclasses because no classes. It has, however, no pull-down menus, just one window, and on it just one canvas. It seemed like a promising candidate for iOS. (The canvas is manipulated by lots of containers that I should be able to port one at a time once I get the basics working.)
I am nowhere. I cannot even position my canvas without the static reference error, usually with a non-existence error as well.
I do not expect offers of an actual solution, but would much appreciate guidance as to how to get traction on this. Can code in a container manipulate a canvas that is outside the container? If so, must I master classes in order to do it?
6 posts - 4 participants