On Dec 26, 2011, at 1:00 PM, use-livecode-requ...@lists.runrev.com wrote:
I reported this to support. Did you too ? Else, please do it ;-)
Yes, I have reported it. Thanks Pierre
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please
Thanks for the suggestion, but that doesn't work either. And set the tool to
browse is just one command that isn't running correctly on startup with 5.0.2.
Does anyone know why now with 5.0.2, preopenstack, startup and openstack
suddenly don't work correctly when you start LiveCode by
Hi Fred,
I can confirm that LC 5.0.2 is not working as expected. The bug you reports is
100% reproductible there. Seems that mothership will have to solve this for us !
Along the tests, i discovered the following :
Some of my stacks are using extensively code to have all component (fields,
Try :
set the tool to browse
HTH,
Le 24 déc. 2011 à 07:30, Warren Samples a écrit :
On 12/23/2011 11:40 PM, Fred Moyer wrote:
Now with this new 5.0.2 that I just purchased, various startup, openstack
and preopenstack commands do not implement -- that is they don't implement
when I
There seems to be a timing problem going on in this case. The same question
was in the forums and a workaround is to set up a separate handler to pick
the browse tool and then do a send in time to call it so taht the browse
tool choice ends up at the end of the queue.
There were problems whether
Now with this new 5.0.2 that I just purchased, various startup, openstack and
preopenstack commands do not implement -- that is they don't implement when I
double-click on the stack while LiveCode is not running. (Everything works fine
if LiveCode is already running.) But, for example, if you
On 12/23/2011 11:40 PM, Fred Moyer wrote:
Now with this new 5.0.2 that I just purchased, various startup, openstack and
preopenstack commands do not implement -- that is they don't implement when I
double-click on the stack while LiveCode is not running. (Everything works fine
if LiveCode is
