XML Feeds

.

[javascript-dev] js disobeys law of cause and effect

evan.raskob [lists] lists at lowfrequency.org
Tue Nov 6 14:03:36 MST 2007


I guess there's no way around it:

http://lowfrequency.org/stuff/js-lcd-draw-test.zip

I don't want to make it public, but there it is.  I'll take it down  
soon.


Thanks
Evan


On Nov 6, 2007, at 6:22 PM, Wesley Smith wrote:

> While I understand roughly form your desription what's going on,
> there's no way to really help you without an actual script and patch.
>
> wes
>
> On 11/6/07, evan.raskob [lists] <lists at lowfrequency.org> wrote:
>> Hello,
>>
>> I am banging my head against the wall with a very strange javascript
>> problem.
>>
>> I've always assumed that messages passed from a javascript outlet
>> occur in the order I send them.  Apparently, this is not the case.
>>
>> I have code to draw on jit.lcd automatically - it should move the pen
>> to an initial spot ("moveto x y"), send a bang (so that the pen is
>> updated), then get the dimensions of jit.lcd ("getdim").   I have a
>> function "dim (x,y)" that should receive the jit.lcd dimensions, and
>> in turn query it for the pen location (via the "getpenloc" message to
>> jit.lcd).  I have a function in js called "penloc (x,y)" that should
>> receive data from the jit.lcd telling me where the pen is located so
>> i can continue drawing.  Sounds very simple, no? In reality, I run
>> the code and see the message "getdim" which triggered the "getpenloc"
>> message AT THE END of the output from the js object.  Which makes no
>> sense, because getdim would have to be sent in order to trigger the
>> drawing in the first place.  Also, the "clear" message to jit.lcd is
>> executed LAST, even though it appears in the max window as having
>> been sent in the proper order (FIRST).
>>
>> In fact, the entire output seems absolutely arbitrary to me, with
>> "getpenloc" calls all stacked in a row (or not at all).  I have tried
>> using immediate mode to see if there is a difference, and tried
>> adding and subtracting [deferlow] and [jit.qball] objects after both
>> the jit.lcd and the js, but no hope.
>>
>> Please help!
>>
>>
>>
>> -Evan
>>
>> _______________________________________________
>> javascript-dev mailing list
>> javascript-dev at cycling74.com
>> http://www.cycling74.com/mailman/listinfo/javascript-dev
>>
> _______________________________________________
> javascript-dev mailing list
> javascript-dev at cycling74.com
> http://www.cycling74.com/mailman/listinfo/javascript-dev



More information about the javascript-dev mailing list