The answer to that question may be academic. But the best answer I can come up with is that mobile devices are fundamentally different than desktop devices. It's already an amazing thing to get a single layout to display in the various desktop operating systems in a consistent manner, and Windows/Mac/Unix/Linux are similar enough for that. iOS and Android are vastly different interfaces, so to look and behave "natively" on these requires in many instances a different kind of object.
It is not a big chore, but you can create your own "scalable" radio buttons from regular buttons and some reasonably high resolution images, or even just the images themselves. That is one of the great things about livecode. You can with some ingenuity create your own custom controls. Bob S > On Oct 22, 2017, at 05:35 , Pyyhtiä Christer via use-livecode > <email@example.com> wrote: > > When fixing a problem with non-scaling radio buttons one solution was to use > widget switch button, which can be scaled. > > Now it appears that those buttons do not retain the setup theme, but you need > to redo it at every stack startup. Why not. > > Actually the first question is why can't the LiveCode team make the radio > buttons scalable? Using those on a mobile device you hardly see what the > hilite status is. > > > Christer Pyyhtiä > chris...@mindcrea.com > > > _______________________________________________ > use-livecode mailing list > firstname.lastname@example.org > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list email@example.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode