Author Topic: UX inconsistency (Dynamic Crop)  (Read 3168 times)

Offline blave549

  • Newcomer
  • Posts: 18
UX inconsistency (Dynamic Crop)
« on: 2013 August 21 08:46:12 »
Hi,

I am a reasonably new user of PI, but have been burning the midnight oil to try to come up to speed.

Yesterday I had a situation where I wanted to apply the same Dynamic Crop parameters to several subs. It did not work the way I expected it to -- i.e. the way other Processes that I've used work. My expectation is that once I have identified a crop area, I could drag the "New Instance" triangle to any image (including the one that I have defined the crop area on) and the crop would be applied. However, as everyone here probably knows that's not the way it works; the green check arrow applies the crop to the sub that the crop area is defined on, but (as I learned only through some Google searching) I have to drag a New Instance onto the workspace and then apply that to other images. That seems not only a bit tedious but as I said at the outset, inconsistent.

The PI UI and associated user experience is, as we all know, a very different beast and I'm learning to love most things about it; in many ways it's the most elegant UI I've ever used. This particular thing though, I do not love  ;).

thanks,

Dave B.
San Jose, CA


Offline naavis

  • Member
  • *
  • Posts: 66
Re: UX inconsistency (Dynamic Crop)
« Reply #1 on: 2013 August 21 08:49:01 »
Hi,

I am a reasonably new user of PI, but have been burning the midnight oil to try to come up to speed.

Yesterday I had a situation where I wanted to apply the same Dynamic Crop parameters to several subs. It did not work the way I expected it to -- i.e. the way other Processes that I've used work. My expectation is that once I have identified a crop area, I could drag the "New Instance" triangle to any image (including the one that I have defined the crop area on) and the crop would be applied. However, as everyone here probably knows that's not the way it works; the green check arrow applies the crop to the sub that the crop area is defined on, but (as I learned only through some Google searching) I have to drag a New Instance onto the workspace and then apply that to other images. That seems not only a bit tedious but as I said at the outset, inconsistent.

The PI UI and associated user experience is, as we all know, a very different beast and I'm learning to love most things about it; in many ways it's the most elegant UI I've ever used. This particular thing though, I do not love  ;).

thanks,

Dave B.
San Jose, CA

I think this same paradigm applies to all Dynamic processes, like DynamicCrop, DBE and DynamicPSF. The defining thing in dynamic processes is that they're all tied to a specific target image, and that's why you can't apply them directly to other images. You have to create process icon and spawn new instaces that are tied to new images.
Samuli Vuorinen

Offline Nocturnal

  • PixInsight Jedi Council Member
  • *******
  • Posts: 2727
    • http://www.carpephoton.com
Re: UX inconsistency (Dynamic Crop)
« Reply #2 on: 2013 August 21 11:02:58 »
Yes, sometimes you end up scratching your head when using PI. And sometimes you smile in amazement. It sortof evens out :)
Best,

    Sander
---
Edge HD 1100
QHY-8 for imaging, IMG0H mono for guiding, video cameras for occulations
ASI224, QHY5L-IIc
HyperStar3
WO-M110ED+FR-III/TRF-2008
Takahashi EM-400
PIxInsight, DeepSkyStacker, PHD, Nebulosity

Offline blave549

  • Newcomer
  • Posts: 18
Re: UX inconsistency (Dynamic Crop)
« Reply #3 on: 2013 August 21 12:41:23 »
That is the truth of it! Well said.

My first "amazed smile" was when I learned of the "drag the title of this sub over to that sub to get the same view/zoom level".  I use that *all of the time*.  Things like that (not to mention some of the end results I've gotten) have made me almost completely quit using PS, and I have a substantial amount of $ invested in PS and the various plugins.

thanks,

Dave.

Yes, sometimes you end up scratching your head when using PI. And sometimes you smile in amazement. It sortof evens out :)