About monorail widget (Merged threads)

[DVkid07]

Progress is a funny thing, in that it seldom comes when you want it to.

I've had very little progress on the graphics or the color controls.

But I might have had a small breakthrough on Tiger compatibility. I have a big folder full of Quartz macro patches that I've collected from websites, discussion lists, and fellow Quartz-heads and came just a few minutes ago remembered one that might be able to control these doors perfectly. It doesn't work exactly as it should just yet, but with a little caressing it should be great.

[DVkid07]

Victory!

I now have two Macro patches, one labeled Leopard Only and one labeled Tiger and Leopard. Each works in the obvious operating systems. And I've begun to work with Host Info in hopes that Quartz can automatically determine during playback what features are available to it. When on Tiger, it will automatically degrade to the simpler controller.

It feels odd to finally solve a problem that has pestered me for such a long time. But it was one of the big roadblocks keeping me from wanting to spend time on this project. And now its almost completely gone. Once that Host Info segment is configured, everything will "just work" regardless of what version you're on.

[DVkid07]

And here it is:

http://files.stevensokulski.com/qmon...ontrollers.qtz

In this file, you'll find the macro patch "10.4 or 10.5 Door Controller." That belongs in the main qMonorail.qtz file. You're going to actually be removing some patches from the file, as I've moved some of the counting functions into the macro patch. Find the current door control patch, labeled "Transition Recyclable" and paste the new patch just below this one. Follow the "Trigger" input of the old patch back to where the "Logic" patch connects to the "Counter." Connect the "Result" of the "Logic" patch to the "Trigger" input of the new door control patch.

Next, connect the "Door Offset" output of the new "10.4 or 10.5 Door Controller" macro patch to the "Input" of the "door_offset" splitter that the old "Transition Recyclable" patch is connected to. Test it to make sure its connected properly, and then delete the "Counter," "Math," and "Transition Recyclable" patches.

You'll probably notice that this doesn't work in the 10.4 Runtime environment. Unfortunately, the Host Info patch still reads 10.5.* even when running in a 10.4.* test environment. But on an actual 10.4 machine, this should work great.

It works by determining what version of Mac OS the host computer is running, and selecting the correct version of the door controller accordingly. That way, Leopard users still get the slick recycling door transition and Tiger users get the proper back and forth motion.

[KAN]

That is very cool that you figured out how to make it work!!!

I had a feeling we could do something with Host Info.

I honestly think my version of QC is shot. I might try to re-install it. I've set up an input to "Transition Recyclable", and hooked that up to a duplicate of the first logic patch. The input says true, the operand is "NOT", with the second false, and the output is still false. Urgg!!!

I will definately try to look at that when I get home. It seems like it should work. You know the way you made the "Trigger" stay true if the right button was clicked once and the coordinates were correct? I may try to do something like that for the color. Any way, I'll slap your compositon in a Widget, and maybe we can have a local Tiger user try it...

Get well soon!

[DVkid07]

Originally Posted by KAN

I honestly think my version of QC is shot. I might try to re-install it. I've set up an input to "Transition Recyclable", and hooked that up to a duplicate of the first logic patch. The input says true, the operand is "NOT", with the second false, and the output is still false. Urgg!!!

That's odd. I can try sending my QTZ over to you so that you could see exactly how I've got it wired. Or you can send me yours, and I'll see if anything looks awry.

Keep in mind that Quartz Composer is really just a means for us to manipulate Core Image information in a user-interface. If there were a problem with patches not showing up, that might be a Quartz Composer issue. But if its actually with values not showing correctly, it might go a little deeper than that.

I will definately try to look at that when I get home. It seems like it should work. You know the way you made the "Trigger" stay true if the right button was clicked once and the coordinates were correct.

I've to some conditional logic on one of my versions of qMonorail.qtz that determines which of the cars the user is clicking on , 2 3 or 4. My thought was to use car 2 as the increasing signal, and car 4 as the decreasing signal. The use a counter+math module to cycle through however many color choices we decide on.

I'm on campus, but I'm free for the next two hours so I'll try and cook it up and post it.

[DVkid07]

Done! Wow, that was easier than I expected.

Now if only my FTP server would let me upload it...

EDIT: Here it is:
http://files.stevensokulski.com/qmonorail/qMonorail.qtz
This file includes both the color controls (left and right) and the new Tiger/Leopard door controls.

EDIT AGAIN:
Just added a simple set of interior images. I want to change them out 'cause I'm not happy with the contrast, but heres what it looks like. And the files are already in the qtz linked to above.

[DisneyImagineering]

Amazing Progress!

[KAN]

So in theory, the patch with a note should work, yet my version of QC is bad. I really need to re-install it.

Here's the file.

Also, note how I eliminated the middleman, and instead of forcing it to make a version decision, just cut straight to Leopard and Tiger.

[DVkid07]

Originally Posted by KAN

Also, note how I eliminated the middleman, and instead of forcing it to make a version decision, just cut straight to Leopard and Tiger.

Not sure what you mean here? I didn't notice any differences in how you handled this.

So apparently there's some issue in Dashboard that is making QTZ files REALLY tough to use in widgets. I'm trying to figure out what's up, but the version I had (the widget that wasn't Tiger compatible) isn't working right now...

[KAN]

Here, I made the file a little more clear.

(Sorry I was a little vague in the beginning about this)



testMonorail

So, DVkid07, I can see the values on other patches that other people inserted are working, but the patches I put in just don't seem to like me. Do you have any clue of what this could mean?

[KAN]

Happy 100th, my thread!!!



So, any progress worth mentioning?

Gracias!

[DVkid07]

Originally Posted by KAN

Here, I made the file a little more clear.

(Sorry I was a little vague in the beginning about this)



testMonorail

So, DVkid07, I can see the values on other patches that other people inserted are working, but the patches I put in just don't seem to like me. Do you have any clue of what this could mean?

Got it! But the reason I put the logic in to determine the host is to avoid anyone who can have the more fluid door movement getting the jerkier Tiger patch. The Leopard method is more sustainable and less resource heavy. If the user can run it, then should.

Did you see my post above about Widget QTZ problems?

[KAN]

Originally Posted by DVkid07

Did you see my post above about Widget QTZ problems?

I'll see if I can try putting it into a widget when I get home...

The QC problem is really bugging me. It is between the two diagnostics you suggested. The patches you put in work, along with any patches I put in before this glich started occuring. Now, any patches I insert have null values. It is very confusing. Other than that, all the other patches work. Does this suggest that it is a problem with Core Image information of QC?

I can can reinstall DashCode, as it is not hidden in the X-Code package of my Leopard Install Disk no. 2. DashCode is outside the bundle of all the X-Code stuff, there clear as day. I can't seem to find Quartz Composer in the bundle of X-Code.

As I said before, I'll try to whip up a quick widget and see if it works.

[KAN]

I believe I have to admit me being hopeless about QC. I posted my "problem" online, and found I had to use a consumer patch. Should have listened to you.

I've been working on it for a while, and I am working on a way to make the color work. It works fine running it in Leopard, yet when I emulate it in Tiger, the colors change occasionally, yet the colors are way off.
eg: ' ' + 'b' = orange. Not blue.
I think it has something to do with the resetting.

So, I think I can figure out how to change the color sucessfully.

Any updates from you?


Also, I put the composition in a widget, and it worked fine, aside the normal problems of loading without a default image. (Don't worry, it is only a blank space since there is no default pic, it can easily be fixed when I put one in.)

[KAN]

UPDATE: To those running a PC, I am in the process of putting the widget online. Unfortunately, I won't be able to post DM7MW: 2.0, but I will keep trying. You can check the process of it online here: Disneyland Mark VII Monorail Widget