HI Richard, I just got a response in the way of a work around...
*As a workaround you can explicitly disable the use of shared memory by passing the -sharedoff parameter to the engine on the command line, which will allow the app to display correctly. Note that this parameter will also work with any standalone applications built with LiveCode. * So, my next question is where do you find the list of all the parameters? I checked and this one is not in the dictionary and I suspect there may be more. This is the second key memory issue we have come across on Linux ( the previous one was the memory leak which was recently fixed) and we hope that we won't find any more as it really slows us down. regards, Glen On Thu, May 31, 2012 at 11:19 AM, Richard Gaskin <ambassa...@fourthworld.com > wrote: > Glen, were you able to turn up any answers on this? > > Have you been able to find any other app which exhibits similar behavior? > > -- > Richard Gaskin > Fourth World > LiveCode training and consulting: http://www.fourthworld.com > Webzine for LiveCode developers: http://www.LiveCodeJournal.com > LiveCode Journal blog: > http://LiveCodejournal.com/**blog.irv<http://LiveCodejournal.com/blog.irv> > > > Glen Bojsza wrote: > > I have two linux machines (A and B) >> >> on Linux machine A I have a Livecode application >> >> on Linux machine B I : >> >> - ssh -X machineA at 192.168.15.6 >> >> >> - launch the Livecode application on machine A but gets displayed on >> machine B >> >> >> When you do this with any other linux applications everything works fine. >> >> With Livecode only the application frame shows up with odd pieces of the >> application components (ie buttons or fields). >> >> You can move the mouse over the area which causes some of the other parts >> of the Livecode application to show but we never see the entire >> application?? >> >> This should work flawlessly like all other Linux applications but doesn't. >> >> Is there some setting or configuration that is required? >> >> It seems strange that only Livecode doesn't work. >> >> I appreciate any advice that can explain the issue and better yet solve >> it... unless it is another bug. >> >> thanks, >> >> Glen >> > > > ______________________________**_________________ > 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<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
