I've said this before, and perhaps it bears repeating. Many apps do not support resizing simply because the nature of the app does not lend itself to it. We use an ERP called eAutomate. If you try to load the app on a monitor below a minimum resolution, it bugs out and fails to display a detail pane. And if on a larger monitor you decide to increase the Windows display percentage to make text more readable, anything above 125% bugs the app in a different way. This is a very popular service management application in use throughout the world. Our users constantly complain about readability on their monitors. The company's response is, sorry. It has to be that way given the amount of information we need to show at any given time.
For an app to be resizable, it has to be designed from the ground up to be so. It's not a simple thing to do, and there is no magic bullet. If a single screen has many hundreds of controls, I begin to question whether or not screen resizing was something the developer had in mind when he started. The way I handle cards with a lot of controls is I use the Tab button, then create a group for each tab. On menuPick I hide ALL the groups, then show the group for the one tab. It's set up in such a way that all I have to do is properly name the group and the tab, and it "just works". Bob S > On Aug 20, 2018, at 18:49 , Monte Goulding via use-livecode > <use-livecode@lists.runrev.com> wrote: > >> On 21 Aug 2018, at 11:32 am, Richard Gaskin via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> - In this thread we have at least half a dozen people, including two from >> the core team, all working together to explore various options for placing >> one object within a resizing method chosen for its ostensible ease of use. :) > > Hmm… I only see one response from core team and it was from me responding to > your queries about when you might get an orientationChanged message and not > get a resizeStack message. I did not make any recommendation about which of > those handlers to do object placement in if that’s what you are suggesting. > By definition if you want to script layout changes when the stack changes > size doing so in resizeStack is the only place that makes any sense. > > If you want to use a fullscreenMode on mobile and have an app with layouts > for portrait and landscape then use mobileSetFullScreenRectForOrientations to > set the rects you want the stack to be for each orientation then handle > resizeStack to update the layout. > > Cheers > > Monte _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
