New '<Shift> @ ' function needed.

maybe i'm misunderstanding...
staring in 2.3 SelectLast, Shift Enter and Shift At remember their last 5 commands and loop back to the first after that.
so Shift At should still be the same, as long as you only press it once... ?

I want to recall "Last Params " as the name suggests, not the last channel number used with it. And it does not remember standard "1@ 50%" type of commands. You have to say 1 Intensity @ 50% to get it to point a channel 1. Now '<shift @' may post a command to modify shutters on a light I adjusted and hour before.

Well I wouldn't call these 'half-assed' changes, they greatly speed up programming.

Can I just double check you're asking for something new, not something that was lost?

I downgrade my mac to 2.2.1 to see the old behaviour and couldn't reproduce what you're asking for!

The CIA is there for Parameter selection, for things like Shutters must of use have 4 macros (some even more) which select Shut In 1+3 together, Shut In 2+4 together, then 2 more for Angle. We then just use +% & -% for adjustment.

For Parameters you don't need the @ just the value. So to adjust the shut values, select the light hit 2 macros to select all 4 shutter 5 Enter will give me 50% on my shutters.

Well, something WAS lost moving to 2.3.x. As I stated earlier, only channel selections using explicit parameters, not the default (intensity) parameter as in ' Chan 1 @ 50%', will be remembered for recall with '<Shift> @', as was NOT the case for 2.2.x.

Prior to 2.3, I had direct select macros labeled"@50", "@55", "@60" etc , for use with indecisive designers who couldn't quite nail a level on the first three attempts. When '<Shift> @' came into existence, I embedded it into those macros because it could be used on NP's as well as the default, without having the parameter explicitly in the macro.

It was almost like '+%' and '-%' keys. However, unlike '+%' , I had to have completed one command before it would post the correct channel instead of the previous one.

After upgrading, when I accidently pressed the "@50" macro recently and four shutters on a VL moved to 50 percent live, a light I hadn't touched for an hour, I knew I had yet another issue with 2.3. So I had to separate out the '<Shift> @' into its own button, requiring two presses for each use of the "@"macros. Now, if I press the "@50" macro on an empty command line it will post "Chan 50 <enter>" . At least its safe, anyway. (If you type "@ 50 <Enter>" you get a error message instead)

The only macros I left as they were are the '<Shift>@+01" and '<Shift>@+-01' macros. Using the '+%' and '-%' is good for big jumps, but at some point you need to fine tune it. I can't use them for intensity unless I press the "intensity" softkey first.

Ever since version 1.0 I was waiting for something like '+%' and '-%' that would take explicit values. Maybe it will be a shift override, like '<Shift> +% 50 <Enter>'.

I was hoping '<Shift @' would be like '@' , but for all parameters. ETC came close, but blew it.

It seems to me the if ETC wants us to use macros to get around ergonomic issues, then they should stop fiddling with the commands we use to write those macros.

Well, something WAS lost moving to 2.3.x. As I stated earlier, only channel selections using explicit parameters, not the default (intensity) parameter as in ' Chan 1 @ 50%', will be remembered for recall with '<Shift> @', as was NOT the case for 2.2.x.

Prior to 2.3, I had direct select macros labeled"@50", "@55", "@60" etc , for use with indecisive designers who couldn't quite nail a level on the first three attempts. When '<Shift> @' came into existence, I embedded it into those macros because it could be used on NP's as well as the default, without having the parameter explicitly in the macro.

It was almost like '+%' and '-%' keys. However, unlike '+%' , I had to have completed one command before it would post the correct channel instead of the previous one.

After upgrading, when I accidently pressed the "@50" macro recently and four shutters on a VL moved to 50 percent live, a light I hadn't touched for an hour, I knew I had yet another issue with 2.3. So I had to separate out the '<Shift> @' into its own button, requiring two presses for each use of the "@"macros. Now, if I press the "@50" macro on an empty command line it will post "Chan 50 <enter>" . At least its safe, anyway. (If you type "@ 50 <Enter>" you get a error message instead)

The only macros I left as they were are the '<Shift>@+01" and '<Shift>@+-01' macros. Using the '+%' and '-%' is good for big jumps, but at some point you need to fine tune it. I can't use them for intensity unless I press the "intensity" softkey first.

Ever since version 1.0 I was waiting for something like '+%' and '-%' that would take explicit values. Maybe it will be a shift override, like '<Shift> +% 50 <Enter>'.

I was hoping '<Shift @' would be like '@' , but for all parameters. ETC came close, but blew it.

It seems to me the if ETC wants us to use macros to get around ergonomic issues, then they should stop fiddling with the commands we use to write those macros.

I've gone back to 2.2.1 and had another play and I've now worked out what you're seeing, your examples are not very clear!

Yes this function has change and I'll vote to keep it as it now as this is much more useful.

ETC do not want you to use macros! But you are using macro because you don't want to type.
I have every few macros and when I watch other programmers programme with lots of macro they spend more time change displays or finding their macro when they would have if they used 3 keys!

As for your macro's I'd remove the Shift+@ so you have your steps for intensity!
If you do need to adjust Parameters you could make another macro which is simply Shift+@.
So when you say, 1 Cyan 50
and you want to change Cyan to 60, use the Shift+@ macro (or just use the keys)
@60 macro to change the Cyan to 60.

You can't make cakes without breaking a few eggs, as ETC add more functions things need to change.
If you want to influence the changes, I suggest you get involved with the beta programme using a offline machine.
The beta programme advances the platform but that involves eggs!