LassoTalk
-
Current Message
On Feb 18, 2012, at 6:04 AM, Kyle Jessup wrote:
> Clearly, we add and fix more compatibility issue with each revision, so this is something getting better and better.
Thanks for taking the time to provide a detailed reply Kyle.
Not exactly what I wanted to read, but at least I know now.
-brian.
#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso
Lasso@lists.lassosoft.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>
-
Current Thread
-
having a brain fade on references in custom types
so, I'm having a problem with code not acting as I had expected it. Perhaps I'm just missing something but I swear that I've done this before and it worked. Working in lasso9. so, I have a custo...
-
Re: having a brain fade on references in custom types
On Feb 17, 2012, at 10:31 AM, Tim Taplin wrote: > so, I'm having a problem with code not acting as I had expected it. Perhaps I'm just missing something but I swear that I've done this before and i...
-
Re: having a brain fade on references in custom types
On Feb 17, 2012, at 7:47 AM, Kyle Jessup wrote: > Also, I see you are using the blah->'foo' syntax (quoted member name). If you are doing that on anything other than self-> then you are taking adva...
-
Re: having a brain fade on references in custom types
thanks for the pointer and reminder. I will have to rethink how I'm using my methods. however, the example that I supplied is not a thread type. flexAPI is a normal custom type with a simple map el...
-
Re: having a brain fade on references in custom types
hmm, so typing that up made something click. and I tested a slightly different approach: local('test' = #flextest) and then retrieved using #test->'storage' and got the results I was expecti...
-
Re: having a brain fade on references in custom types
On Feb 17, 2012, at 10:59 AM, Tim Taplin wrote: > thanks for the pointer and reminder. I will have to rethink how I'm using my methods. > > however, the example that I supplied is not a thread t...
-
Re: having a brain fade on references in custom types
hmm, still struggling a bit with this, but one light just went on that I think is the key. It looks like if I recast the property, it breaks the reference. so where I was updating the 'storage' by...
-
Re: having a brain fade on references in custom types
On Feb 17, 2012, at 12:42 PM, Tim Taplin wrote: > hmm, still struggling a bit with this, but one light just went on that I think is the key. It looks like if I recast the property, it breaks the re...
-
Re: having a brain fade on references in custom types
On Feb 17, 2012, at 7:53 AM, Brian K. Middendorf wrote: > On Feb 17, 2012, at 7:47 AM, Kyle Jessup wrote: > >> Also, I see you are using the blah->'foo' syntax (quoted member name). If you are d...
-
Re: having a brain fade on references in custom types
On 2012-02-17, at 3:43 PM, Brian K. Middendorf wrote: > Does silence = yes? No, silence == Kyle was doing family stuff this afternoon, took an early afternoon. "Official" answer to come from...
-
Re: having a brain fade on references in custom types
On Feb 17, 2012, at 10:53 AM, Brian K. Middendorf wrote: > On Feb 17, 2012, at 7:47 AM, Kyle Jessup wrote: > >> Also, I see you are using the blah->'foo' syntax (quoted member name). If you are do...
-
Re: having a brain fade on references in custom types
On Feb 18, 2012, at 6:04 AM, Kyle Jessup wrote: > Clearly, we add and fix more compatibility issue with each revision, so this is something getting better and better. Thanks for taking the time...
To find out more about this list or how to subscribe - choose the 'i' next to the list name on the right, or click here for more information about LassoTalk
Lasso Talk
RSS Feedcommunity
Related Technologies
