Re: [Finale] More Quickeys problems
I loved OneClick. Had it set up beautifully for OS9. As I was about to install OS X I contacted them and was dismayed to learn that OC would not work with OS X. However, as my workload was diminishing anyway I went for OS X. I have no macro program ay present but it doesn't seem to slow me down too much. Stan Lord On 8 Mar 2005, at 17:09, Johannes Gebauer wrote: Nothing I have seen on OS X even comes close to what OneClick could do in OS 9. I don't know OneClick very well but I don't think it had logic and variables. QK3 is very powerful and so there is a bit of a learning curve (just like Finale). As in Finale, QK3 allows you to do the same thing in many different ways. Sometimes it is frustrating learning the best approach but over time you will be as comfortable with QK as you are with Finale. You don't know OneClick very well. OneClick was a complete programming language for macros. Of course it had variables, of course it had logic. It was 1000 times more powerful than Quickeys X. And it was easier to use, as well. And fast, including the editor. I have already pretty much decided against Quickeys. It doesn't offer that much more than iKey to justify more than 3 times the price. Johannes -- http://www.musikmanufaktur.com http://www.camerata-berolinensis.de ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
[Finale] More Quickeys problems
I think I am going to give up on Quickeys. There are so many problems... 1) When I try to record a complex macro in Finale, Quickeys regularly crashes. 2) I am trying to get a Macro to select a popup menu item in the Frame Attributes Dialog. I am trying to change a textblock from Single Page to Page Range. Either this doesn't work at all, or, if it does work, for some reason the second page range text field doesn't become active. I am sure this is partly Finale's fault, but it has already taken me almost a day now, without success. 3) Although not as bad as iKey2, the user interface isn't exactly wonderful either. 4) The editor is so slow. 5) Programming complex macros is actually more fiddle than with iKey 2. Unless someone can tell me the solutions to all of this I am going to go back to iKey. I have to decide whether I want to put up with the iKey2 UI or reprogram my macros in iKey 1, but either seems to be better than Quickeys. Programming the complex macro I am currently trying in Quickeys took me about half an hour in iKey 2. It's pretty sad, since Quickeys can obviously do much more (ie it has variables which I would like to use). Nothing I have seen on OS X even comes close to what OneClick could do in OS 9. Johannes -- http://www.musikmanufaktur.com http://www.camerata-berolinensis.de ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] More Quickeys problems
1) When I try to record a complex macro in Finale, Quickeys regularly crashes. Doesn't happen to me, I have it do all manner of things and it has never, never crashed, even during the longest macros. -- Simon Troup Digital Music Art - Finale IRC channel server: irc.chatspike.net port: 6667 channel: #Finale - ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] More Quickeys problems
Johannes, Why were you using iKey 2? It has almost no added functionality over iKey 1. If you don't need a macro program that can test for the states of menu items, as in checked or unchecked, or for variables iKey 1 will work for you, and costs a fraction of Quickeys. steve On Mar 8, 2005, at 7:25 AM, Johannes Gebauer wrote: I think I am going to give up on Quickeys. There are so many problems... 1) When I try to record a complex macro in Finale, Quickeys regularly crashes. 2) I am trying to get a Macro to select a popup menu item in the Frame Attributes Dialog. I am trying to change a textblock from Single Page to Page Range. Either this doesn't work at all, or, if it does work, for some reason the second page range text field doesn't become active. I am sure this is partly Finale's fault, but it has already taken me almost a day now, without success. 3) Although not as bad as iKey2, the user interface isn't exactly wonderful either. 4) The editor is so slow. 5) Programming complex macros is actually more fiddle than with iKey 2. Unless someone can tell me the solutions to all of this I am going to go back to iKey. I have to decide whether I want to put up with the iKey2 UI or reprogram my macros in iKey 1, but either seems to be better than Quickeys. Programming the complex macro I am currently trying in Quickeys took me about half an hour in iKey 2. It's pretty sad, since Quickeys can obviously do much more (ie it has variables which I would like to use). Nothing I have seen on OS X even comes close to what OneClick could do in OS 9. Johannes -- http://www.musikmanufaktur.com http://www.camerata-berolinensis.de ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] More Quickeys problems
In the recording tab in the preferences, do you have Do exhaustive... checked or unchecked? Johannes Simon Troup wrote: 1) When I try to record a complex macro in Finale, Quickeys regularly crashes. Doesn't happen to me, I have it do all manner of things and it has never, never crashed, even during the longest macros. -- http://www.musikmanufaktur.com http://www.camerata-berolinensis.de ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] More Quickeys problems
Nothing I have seen on OS X even comes close to what OneClick could do in OS 9. I don't know OneClick very well but I don't think it had logic and variables. QK3 is very powerful and so there is a bit of a learning curve (just like Finale). As in Finale, QK3 allows you to do the same thing in many different ways. Sometimes it is frustrating learning the best approach but over time you will be as comfortable with QK as you are with Finale. You don't know OneClick very well. OneClick was a complete programming language for macros. Of course it had variables, of course it had logic. It was 1000 times more powerful than Quickeys X. And it was easier to use, as well. And fast, including the editor. I have already pretty much decided against Quickeys. It doesn't offer that much more than iKey to justify more than 3 times the price. Johannes -- http://www.musikmanufaktur.com http://www.camerata-berolinensis.de ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] More Quickeys problems
Steve Gibons wrote: Johannes, Why were you using iKey 2? It has almost no added functionality over iKey 1. If you don't need a macro program that can test for the states of menu items, as in checked or unchecked, or for variables iKey 1 will work for you, and costs a fraction of Quickeys. The reason I am on iKey 2 is because when I registered it had just come out. After I had it installed there seems to be no way to go back without having to reprogram all macros. A lot of time has already gone into them, so since I may have to reprogram them anyway I wanted to see whether QKs is better. The problem with iKey is this: The author doesn't really seem to understand the concerns about iKey 2. So iKey 2 is the direction it's going to go. What am I going to do if Tiger destroys iKey 1 compatibility? It is very unlikely that iKey 1 will be updated for any future incompatibilities. So then I will have to go iKey 2 anyway. This is a real dilemma. Actually, I could really do with both variables _and_ checking the state of menu items. Johannes Johannes -- http://www.musikmanufaktur.com http://www.camerata-berolinensis.de ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] More Quickeys problems
In the recording tab in the preferences, do you have Do exhaustive... checked or unchecked? Unchecked. With regard to popup menus, when recording macros, do everything as though you were in slow motion. Hold the popup menu selection for a second before selecting, don't click ok for a second after it's selected, when you do click OK, hold it down for a second before you let go. This gives quickeys the best possible chance of seeing what you're doing. I've had little trouble since doing things this way. Always make sure the weird green shaded focus effect is with you! -- Simon Troup Digital Music Art - Finale IRC channel server: irc.chatspike.net port: 6667 channel: #Finale - ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] More Quickeys problems
I have already pretty much decided against Quickeys. It doesn't offer that much more than iKey to justify more than 3 times the price. I know it's expensive, but for me the only calculation was is it worth $99 or whatever for the time it saves me. For me the answer is a resounding yes. Mind you, I've been using it since it was released way, way back, and so have only ever paid upgrade prices ever since. I'd encourage you to stick with it Johannes, it took me a week to get my head how to make it work best on my system - since that time I've moved from time defecit to time = money profit, hand over fist. -- Simon Troup Digital Music Art - Finale IRC channel server: irc.chatspike.net port: 6667 channel: #Finale - ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
