|
|
Extra Patcherator in Extra Editor/ Patch Inspector for Extra Editor / Macro Drag and Drop DuplicateAfter discovering the hidden old style patcherator via QCEditCompositions, I realized that this would be a really nice addition (the OLD style built in patcherator) in the Extra Editor in Kinemecore, since the functionality and layout is already so similar. Also, it would be nice to be able to pull up patch inspector for things in the Extra Editor (kinemecore) (a Patch Inspector available for each window would be ideal), or have the normal patch inspector become active for whatever window is in focus (as opposed to only the main Editor window), so that Settings can be changed inside Extra Editor as well. Thirdly, it would be very snazzy to have a macro icon by the macro title in Extra Editor, that can be dropped onto itself, or back onto the main Editor for instantly making duplicates (a qtz icon in the title bar in QCEditCompositions can be dragged back onto itself to create a duplicate macro).
|
that looks handy to have the patch creator integrated with editor. i wasn't using qc @ version 3 so that looks new to me. still haven't really found a use for the extra editor yet but i think 2 viewers would be an awesome hack even multiple inspector windows would be very handy when you want to tweak settings but not necessarily wanting to publish to root as exposed parameters. right now when you click a patch the inspector switches which is a good work flow and shouldn't be changed but a k core option to leave the inspector windows open and floating could be cool or an option click would open second inspector etc..
is anybody using the extras editor ? and may i ask how you are using it etc..
Yes I use extra editor occasionally (not as much as I thought i would) when I am working simultaneously at the top and bottom of a nest of iterator/transform/trackball patches. Also just to have access to unpublished inputs down the bottom of a macro to trim settings while building the comp higher up.
In iWork apps you can have as many inspectors as you want. Each instance of Inspector pallet has all the tabs if you want to change the inspector with one-click (unlike QC) from say Values to Setting tab in case of QC. When I was doing a lot in Keynote I had heaps of inspectors floating around b/c you are constantly adjusting parameters on lots of the tabs. I'm sure I've requested this in QC at least once.
via radar? can you find the number? (I wasn't able to locate it after doing a few searches and a brute-force of all QC radars with "inspector" in the title)
I suggested on Kineme boards — potentially as part of KinemeCore.
Just filed a request at Apple Bug ID# 8184610.
When cwright pointed out you can use Cmd–Sft–I to get multiple settings patches this need for multiple inspectors was ameliorated quite a bit. Javascript and maths expression are at top of my most need to edit list of patches but that can get confusing at times when you are mistaken about which JS patch you are editing.
Off Topic: I often duplicate a JS patch before I start a new stage of work with it so I have something operational I can fall back on. At times I've seen hours of work go down the drain, although I can't reproduce the JS patch bug I know it's there. And we all know it knows I know ;)
I was ignorant about correct use of _testMode (& null structures) for quite a while so that was potentially part of my frustrating loss of working code. I also have found occasionally JS patches that aren't working when copied to a blank comp will work.
thanks thats a good idea to use the extra editor when you are nested. i knew there had to be a good reason for this. the other day i was building this huge patch i actually think i hit boundaries of the editor for the first time and my fingers got tired of multi-touch scrolling from edge to edge. to bad i didn't even remember there was an extra editor.
generally i would say having more than one inspector is pain. try programming for the ipad in interface builder on a laptop and you will see how all these inspector /document style floating windows actually get in the way of my work flow. it makes want to alloc init every thing in xcode but i think it would be convenient in qc to at least have this option.
On Leopard and later, the editor is of infinite dimensions. On Tiger, it was a fixed size. Unless you're using a super-old OS X, you didn't hit a boundary :)
Yes you need the screen real estate. I get more cramped in for space in QC than Keynote believe_it|!. I like to have JS patches long-vertical with reasonable width and Editor long-horizontal a now I want the Viewer drawer and/or QC Graph Log (long horizontal) + inspectors all getting a bit much! Not as bad as in Adobe CS apps though :)
BTW I just downloaded Safari5 and these page redraws on this site seem twice as fast (is that just me?). I'm wondering if that means JS inside QC is going to be speed-bumped too? Any thoughts, cwright?
The Nitro engine [JS] has been improved in Safari 5 & QC benefits thereby. It also renders the DOM [HTML] quicker too. & more besides ...., especially interested in the Safari extensions program.
...not that it's super useful but when QCEditCompositions is enabled a Quick Look at any .qtz also opens the Loaded Composition List...
...as i said not that useful but can give you a quicklook at the patchwork if you call it from the list...no changes can be saved
...oh and the Loaded Composition List doesn't dissapear as quick as it should...
Hmm, what do you mean by appear/disappear "as quick as it should"? Once it's been activated once, it opens up instantly every time. If you have it open, it's because you want it, so I don't know about the disappearing comment.
You are incorrect, changes can be saved. You take the instance that you have changed, Option+DoubleClick on the corresponding listing in the Loaded Compositions list, and then you are presented with an option to do a Save As to save any edits you have done.
I am really sensitive to doing anything spammy on this site, but since I can see this may end up in a scenario where people don't quite understand how this works fully, or misinfo could get spread as law, I will note that I've written pretty extensively about the ins and outs of this functionality and other QC ins and outs at my website, www.georgetoledo.com
...i mean that when i press spacebar to Quick View a .qtz it shows up together with the Loaded Composition List window, however when i press spacebar or ecs or select a different file the Loaded Composition List Does not dissapear. As seen in attachments. ... Save As is possible as you noted...and i haven't seen all the vimeo videos you posted so didn't know 'bout that... my mistake ...
No worries...
Oh, I see what you mean. Yeah, from whenever you have opened a qtz via a given app, and initiated a Loaded Composition list, that list will always be there for that app, until the app is shutoff. For something like Quicklook, that doesn't really happen! At best, you'll be left with a blank list.
One thing that is sort of cool about the Quicklook method is that you gain access to regular Quicklook features, like the Index sheet. You can command click a number of qtz's, opening them all at once, and then use the Quicklook contact sheet to flip between, or the Previous and Next arrows, which is sort of interesting.
The lag on startup I almost see as a given, since QC is so frigging slow to startup in SL sometimes. I'm curious now, because I don't think the list (or QC) has the same kind of lag time in Leopard, but I wonder if that's a false memory.
It would basically be nice if the little red/yellow/green buttons on the title bar actually worked. What's hilarious is that the green button DOES work, but makes the composition list fullscreen!
Nice revelation of the previously undocumented and little known off features.
I'd like to see QC Editor being capable of being panelled so that these features become available within the Editor, although my concept includes being able to treat each level of a Macro nested object set as a different , editable set of components, with each level within its own panel.
Actually, I think that is also a new feature request, although it fits in pretty well with extending the functionality of the QC Editor including these undocumented features.