![]() The bad thing about doing it this way is that I believe it only affects the way the text is displayed and printed in the document. This isn't an AutoCorrect setting, it's a style definition.Īgain, it doesn't fix the problem of the QuickTime interface, but it might be a functional (and better still, FREE!!) workaround. The best part is that if you are more accustomed to typing in mixed case (which, I realize, you probably aren't) the style definition will "fix it" for you. I believe that within MS Word, you can define a text style to be all-caps, or caps and small caps, or all lower case, heck you might even be able to force autoMaticCamelCasing through the Word style sheets. I don't use Word, so I can't be totally sure, but there may be a tool within Word that would address everybody's needs all at once. I did think of something else that might be an even better workaround, though. And here I was hoping that 7.1 would be the bug-fix settle-down version that made QT-7 as robust as QT-6.5.3 was. ![]() If you've been watching this forum lately, you can see that to the independent observer, it appears that Apple's QuickTime development team has apparently gone stark raving nuts in the past series of revisions, making HUGE changes to the interface without warning anybody, and making QuickTime, something we've all counted on for years to be nice and stable, suddenly something of a moving target. And yes, I understand that this is a change in QuickTime. To point #2, no, it isn't a solution, but it jumped immediately to mind as an add-on that might help. Obviously, you are stuck with whatever standards you are given to work with. You merely gave me a good soap-box from which to rant about it again, and I hope you didn't take offense at it. Well, yes, as to Point #1.I'm a graduate of a Broadcasting program, and well aware of the problem of the persistent standard. I do own a Shuttle Express and think it's a cool little gadget. I don't sell hardware, I have no connection whatsoever to Contour Design, and can't think of any possible way to benefit financially from giving this advice. It isn't really a solution or a workaround to your problem, but it's a tool that might be beneficial to your workflow.ĭisclaimer: That's an unsolicited endorsement. What that means is that not only can you use it as a bi-directional jog/shuttle controller for QuickTime, not only can you program the buttons for, say, set-in, set-out, play-forward, loop, stop.but I'm pretty certain that you can set it up so that while you are TYPING MERRILY AWAY IN ALL CAPS IN MICROSOFT WEIRD, it can still control QuickTime Player *even though QuickTime Player is not the foreground application*. (Okay, Dave, what the heck does all that mean?) Even cooler is that the device focus does not necessarily follow the application focus, but it does follow the mouse pointer. I've got the Shuttle Express which has five buttons (the Shuttle Pro has "a whole bunch"), and the really cool thing about it is that because you can program it on a per-application basis or on a global basis. The neat thing about it is that all of the buttons and functions are completely programmable, and you can even use it to fire off AppleScripts. It's a multimedia controller which plugs into the USB port and emulates a jog/shuttle control found on a professional VCR. □Ģ) Have you considered getting yourself a Shuttle Express or Shuttle Pro controller? I'm trying to remember the manuf.I think it's Contour Design or something like that. OBVIOUSLY YOU HAVE TO LIVE WITH WHATEVER STANDARDS ARE ESTABLISHED BY YOUR CLIENT, EVEN IF THOSE STANDARDS DON'T REALLY MAKE SENSE. THAT SAID, IT MAY NOT REALLY BE YOUR CHOICE. ![]() THIS PARAGRAPH IS IN CAPS NOT BECAUSE I AM TRYING TO SHOUT, WHICH IS THE USUAL INTERPRETATION ON THE INTERNET, BUT TO DEMONSTRATE A POINT: READING THIS PARAGRAPH IS ACTUALLY MADE MORE DIFFICULT BECAUSE OF THE CAPS AS THEY OBSCURE THE SYMBOLS, THE SENTENCE ENDINGS, AND ANY OTHER METHODS WHICH MIGHT BE USEFUL FOR EMPHASIS. ![]() I STILL DO NOT UNDERSTAND WHY MIXED CASE IN A LARGE FONT SIZE, WHICH IS ACTUALLY MUCH EASIER TO READ THAN ALL-CAPS, HAS STILL NOT BECOME THE WORLDWIDE STANDARD. Not really a workaround or a solution, but two things to consider.ġ) DOING SCRIPTS IN ALL CAPS IS AN ARCHAIC PRACTICE WHICH DATES BACK TO THE STONE AGES WHEN THE ONLY WAY TO GET LARGE TEXT WAS TO USE A PRIMARY TYPEWRITER WHICH WAS INCAPABLE OF PRODUCING LOWER CASE TEXT. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |