Ben Houge

Here's something that's been shaking my grip on reality for a few days. In this patch, if I click the bang at the top manually, I get my desired behavior: centered jit.lcd text in the jit.pwindow below. However, if I turn on the metro to bang it automatically, my text is no longer centered.

Oh, BTW, Windows 7 64 bit, 4 GB RAM, Intel dual core P9700 2.8 GHz, Max 5.1.5

PS For bonus points, is there any reason jit.lcd won't recognize most of the fonts on my computer? It can handle Arial and Courrier and that's about it.

Here's something that's been shaking my grip on reality for a few days.  In this patch, if I click the bang at the top manually, I get my desired behavior: centered jit.lcd text in the jit.pwindow below.  However, if I turn on the metro to bang it automatically, my text is no longer centered.

PS For bonus points, is there any reason jit.lcd won't recognize most of the fonts on my computer? It can handle Arial and Courrier and that's about it.


manual-bang-vs-bang-from-metro-weirdness

Using a qmetro fixes problem, I guess it is tripping up on something somewhere.

So would I be correct to think of qmetro as a workaround for a bug in Jitter? It seems like the potential for two different behaviors for the same bang really challenges the stability of the system.

Also, pizza olives, could you explain how a [trigger] might be used in this case? I admit I rarely find a use for that object, but I welcome any chance to improve my Max coding style!

So would I be correct to think of qmetro as a workaround for a bug in Jitter?  It seems like the potential for two different behaviors for the same bang really challenges the stability of the system.

Also, pizza olives, could you explain how a [trigger] might be used in this case?  I admit I rarely find a use for that object, but I welcome any chance to improve my Max coding style!

The real problem here is the getpenloc message. The scheduler defers this message to a lower priority. What you should do is wait for the result of the getpenloc and use that to trigger the next step in the sequence of events, instead of using the uzi. That the qmetro works here is good, but if you understand why, then you know that it is not because of a bug. There is a [next] object that can tell you more about scheduler events. Somewhere in the documentation a chapter is devoted to the scheduler, you should read that.

Awesome, thanks very much for the feedback, you two!

The comment about getpenloc made me smack my forehead, makes a lot of sense.

manual bang vs. bang from metro weirdness