Photoshop: Remote Connections, Photoshop is recording each 1px nudge as a new item in History

  • 1
  • Problem
  • Updated 6 years ago
  • (Edited)
I am using Remote Connections with an app called Skala Preview, which lets you view mockups in Photoshop live on an iOS device. Everything seems to work perfectly except for the way the nudge feature is being recorded in Photoshop's history.

Usually in Photoshop, if you hit the up arrow 10 times, it will nudge a layer 10 pixels, but only record the Nudge action once in the History pane. This is good, because it means that nudging an object a bunch of pixels does not completely fill your History with minute actions.

However, as soon as the Skala Preview Mac app is running and Photoshop (CS6) is utilizing the Remote Connections feature, it records every single Nudge action in the History. This quickly overwrites your entire Photoshop History with 1px nudge actions, and can be a pain.

I contacted the Skala Preview team, and they do not believe it could be a problem on their end: https://twitter.com/bjango/status/221...

Is there any fix for this or reason why it might be intended?
Photo of Tyler Murphy

Tyler Murphy

  • 13 Posts
  • 4 Reply Likes

Posted 6 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
Do you have Nav or other remote connection apps to test?

It sounds like Skala might be doing something after each document change, which would invalidate the last command and force each nudge to record separately. Unfortunately that is unavoidable as long as the remote app does something on each document change (because there really are additional commands after the nudge).
Photo of Tyler Murphy

Tyler Murphy

  • 13 Posts
  • 4 Reply Likes
I only have an iPhone to test on right now so I can't try Nav.

The only thing Skala does after each nudge is display an updated version of Photoshop's canvas on the iOS device. Would that be enough to do it? It does not do anything to record a new command in Photoshop's History.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
OK, so it is executing several commands after each nudge, which means that each nudge has to be recorded as a separate command (because there are other commands not showing up on the history palette).
Photo of Tyler Murphy

Tyler Murphy

  • 13 Posts
  • 4 Reply Likes
Ah, I see. This isn't a high priority issue so I don't know if it's something that needs to get dealt with, but I would make this suggestion: perhaps these invisible commands (not recorded in History) should not interfere with the visible commands in the History. Since the user does not see new events getting recorded, he or she probably doesn't expect the History to function any differently than it generally would (as in, recording lots of 1 px nudges as separate events is probably never desirable)

As it currently stands, you have to Quit apps like this while you work to prevent your History from getting filled up with junk.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
Or increase the number of history states.
It's not so simple to recognize that the intermediate commands from the remote application don't matter to the document (because they could). But I'll see what I can do.