Re: Chipp Walters 3D object viewer stack

2017-09-23 Thread Alejandro Tejada via use-livecode
Hi Colin,

on Sunday Sep 24 2017, Colin Holgate wrote:
> It may be a different one, but is it this?:
> https://github.com/angerangel/LCR3D

LCR3D is the work of Massimiliano Vessi (MaxV)
Chipp Walters stack is a different one.

In the 90's, there was a HyperCard stack that
could open *.obj 3d models too.
Specifically, I remember an impressive
3d whale model. Does anyone remembers
the name of this stack, too?

On Sat, Sep 23, 2017 at 6:46 PM, Alejandro Tejada 
wrote:
>
> Hi All,
>
> I was looking in the mail list archives, the name of
> Chipp Walters Stack that could import and display
> 3d models in *.obj format, but could not find it.
>
> Does anyone remembers the name of this stack
> or could point me to the mail list message where
> Chipp posted it?
>
> I remember that Scott Rossi participated in that
> mail list thread too.
>
> Thanks in advance!
>
> Al
___
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


Re: Chipp Walters 3D object viewer stack

2017-09-23 Thread Colin Holgate via use-livecode
It may be a different one, but is it this?: https://github.com/angerangel/LCR3D

> On Sep 23, 2017, at 3:46 PM, Alejandro Tejada via use-livecode 
>  wrote:
> 
> Hi All,
> 
> I was looking in the mail list archives, the name of
> Chipp Walters Stack that could import and display
> 3d models in *.obj format, but could not find it.
> 
> Does anyone remembers the name of this stack
> or could point me to the mail list message where
> Chipp posted it?
> 
> I remember that Scott Rossi participated in that
> mail list thread too.
> 
> Thanks in advance!
> 
> Al

___
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


Chipp Walters 3D object viewer stack

2017-09-23 Thread Alejandro Tejada via use-livecode
Hi All,

I was looking in the mail list archives, the name of
Chipp Walters Stack that could import and display
3d models in *.obj format, but could not find it.

Does anyone remembers the name of this stack
or could point me to the mail list message where
Chipp posted it?

I remember that Scott Rossi participated in that
mail list thread too.

Thanks in advance!

Al
___
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


Re: Setting the acceleratedRendering to true on startup on

2017-09-23 Thread J. Landman Gay via use-livecode

On 9/23/17 2:27 PM, Sannyasin Brahmanathaswami via use-livecode wrote:

when we issue "wait 200 milliseconds with messages"  does the engine send idle to the 
card? i.e now the phone OS has time to "catch up" ??


Basically. The idle message is sent regularly whenever no other handlers 
are running. The engine uses these idle periods to do housekeeping, 
which I guess you could think of as "catching up."


When you wait with messages, the engine is put into the state where 
"nothing is happening" and so receives idle messages for the period of 
time specified by the wait. It also allows other user actions to execute 
and regular engine messages to be sent normally.


--
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


Re: Script Editor Autocomplete Optional?

2017-09-23 Thread Sannyasin Brahmanathaswami via use-livecode
Monte

Respond to your previous "disheartened"  

don't be!

Just downloaded 9.0.0 DP9

For all the gorilla dust around this new feature which I had not actually see 
yet, I was wondering..

But now, wow this is awesome!

How often to I set an itemdelimiter? sheesh "like all the time"

and auto complete leaves the "characters" selected and when you type a quote, 
wraps it and then keeps it selected so you type underscore and it is inserted. 
Magic!

Thanks for all the hard work on this!

Brahmanathaswami


Jacque wrote:

Having just read the blog post, which I didn't know existed until I saw 
the reference here, I may use autocomplete more than I thought. I didn't 
know it did all that stuff. Apologies, Monte.

I'd still like the separate pane for when I'm not actively coding, but 
this does look pretty cool. I'm fairly amazed at what you've accomplished.

___
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


Re: Setting the acceleratedRendering to true on startup on

2017-09-23 Thread Sannyasin Brahmanathaswami via use-livecode
Dan, yes this could be really helpful

Almost all (but one) use cases in our app framework are simply to facilitate 
either a scrolling field or a scrolling group.

If we are looking for some consistent "algorithm" for this, which I am, so we 
don't have so much mental-re-estate consumed every time we want use it… perhaps 
what works is

1) finish all inits
2) set acceleratedRendering to true at the same time we create our mobile 
scroller
3) set it to false the same time we delete all our mobile controls

if this actually works, then we can just add this to our 
lib_mobileControls.livecodescript "backscript" and it would serve us everywhere 
in all contexts.  Just have to be careful not to be creating any scroller 
inside any *open* handlers.

worth a try. Though I expect Jacque may jump in with more caveats.

Also I believe the "wait with messages"  in effect creates a condition where 
"the app comes to an idle"  Though I'm still not clear on this, Jacque 
explained it briefly once, but going back to the dictionary, even reading the 
entry for wait very carefully.  "wait" shows "idle" as related and "idle" shows 
"wait" as related, but neither indicate exactly what that means.

when we issue "wait 200 milliseconds with messages"  does the engine send idle 
to the card? i.e now the phone OS has time to "catch up" ?? The current 
understanding seems to be that Livecode can "get ahead" of the OS on Android… I 
mean, any app is in effect a "controller" of the OS on the machine. So it's as 
if we have to let Android catch up before doing anything more? sheer guess work 
on my part… Mark would have a better analysis.  But we are seeing another bug 
"resume on Android causes LC to crash" seems to be alleviated if you the stack 
that has a wait handle in the preopenstack handler…so I guess on Android, open 
handlers are firing on resume, even though it appears that you are going and 
coming from an already open stack… another mystery there.

Until this bug (if it is one, since it works fine in iOS I presume it is) is 
fixed, a precise definition of the "best hackaround" in any context will be 
useful, so you are getting close to that.

BR



 

On 9/23/17, 5:21 AM, "use-livecode on behalf of Dan Friedman via use-livecode" 
 wrote:

I had these exact same issues:  black screen if acceleratedRendering was 
enabled on Android at startup.   I found that if I set the acceleratedRendering 
to true after ALL startup items were complete (preOpenCard, preOpenStack, 
openCard, openStack, and whatever else you’re doing at launch – basically when 
the app comes to an idle) the acceleratedRendering then was enabled 
successfully and seemed to work properly from that point on.

That’s my 2 cents.  Hope it helps.

-Dan



___
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

Re: Setting the acceleratedRendering to true on startup on

2017-09-23 Thread Dan Friedman via use-livecode
I had these exact same issues:  black screen if acceleratedRendering was 
enabled on Android at startup.   I found that if I set the acceleratedRendering 
to true after ALL startup items were complete (preOpenCard, preOpenStack, 
openCard, openStack, and whatever else you’re doing at launch – basically when 
the app comes to an idle) the acceleratedRendering then was enabled 
successfully and seemed to work properly from that point on.

That’s my 2 cents.  Hope it helps.

-Dan

___
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