You're right. If the OS doesn't allow it, then clearly Livecode has to enforce it.
Pete Haworth On Mar 12, 2011, at 2:30 PM, Bob Sneidar wrote: > I think the question is, would the OS actually allow it? It may not. I > remember years ago, while working with FoxPro for the mac, that because > Microsoft wanted to have compete control over their menu structure, their > menus were not actually "menus" at all. Because of that, any utilities that > did custom menu modifications would not work with FoxPro. QuicKeys comes to > mind. I was not able to create an action involving menus, because there were > no "Menu's" per se. > > Something to chew on I guess. > > Bob > > > On Mar 12, 2011, at 1:17 PM, Peter Haworth wrote: > >> I almost replied on this topic a couple of days ago when there was another >> user confused by this. >> >> I do agree that the way Livecode arranges menus for the Mac is standard >> behavior for OSX according to Apple's Human Interface Guidelines. My >> problem with what Livecode does is that "standard" and "guidelines" mean >> just that, by which I mean that Livecode should provide a way to do >> non-standard things that don't conform to the guidelines if that's what I >> want to do. It's fine to use the guidelines as a default but there should >> be a way to not take the default and I don't think LiveCode provides one. > > > _______________________________________________ > 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 > _______________________________________________ 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
