It's likely you've never had interference issues with Navigator because users wouldn't be using more than one property inspector simultaneously. But my Zygodact system did interfere with the GLX framework and I had to rewrite it to accommodate GLX. It wasn't how I wanted things to work, but enough people were using GLX at the time that it was necessary. Fixing the problem required communication between me and the author.
The conflict occurred because of different approaches when handling preferences files. Standardization would have avoided the issue. On October 14, 2015 8:59:51 AM CDT, Geoff Canyon <gcan...@gmail.com> wrote: >On Wed, Oct 14, 2015 at 4:14 AM, Mark Waddingham <m...@livecode.com> >wrote: >> Great - how do you ensure that Mark's tools don't interfere with >Geoff's >> so users can use them side-by-side? >> >> If every toolmaker has to take into account every other toolmaker's >'way >> of doing things' you end up with a situation where one individual who >wants >> to write a tool needs to learn about everybody else's if they want to >> distribute it for the benefit of all. > > >I've never found this to be the case. I have never had someone report a >bug >to me because some other tool interfered with Navigator, or because >Navigator tripped up someone else's tool. > -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com _______________________________________________ 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
