Author Topic: Mask States  (Read 2345 times)

Offline ngc1535

  • PixInsight Old Hand
  • ****
  • Posts: 326
Mask States
« on: 2017 October 06 06:19:32 »
Hi,

I am wondering if there is some logic behind the following observation concerning the states of masks.

You can do the following:

1. Apply a mask to an IMAGE (square shows when dragged over). Now IMAGE has a brown tab and mask is associated with IMAGE.
2. Hide the mask (Show mask state), but still have mask enabled. IMAGE tab is still brown.
3. Disable the mask. IMAGE tab is clear. Only indication of mask association is tool bar icon "remove mask" (or under menu).
4. Remove mask. Now mask is gone. However...
5. Apply another mask to IMAGE. Square shows when dragged over. But mask state is still set to hidden and disabled so IMAGE tab is clear. Perhaps it is not obvious that the mask is in place especially because the current active image is the mask (if dragged over). When making IMAGE active only indication is tool bar mask icon (or under menu).

So... two questions:

Would it make sense to have a graphically communicated state by looking at the IMAGE to know that there is a mask associated with it even though it isn't being displayed and isn't enabled? I suggest outlining the (three sides of the) tab with brown instead of filling it.

When a mask is removed from an active image- is there a reason why the mask states not shown and enabled/disabled aren't reset?
Or said another way, under what circumstances do you want to apply a "new" mask in a disabled state? I can see an argument for the show state of a mask remaining hidden perhaps... but not the disabled state.

One area of confusion occurs (if you do not look a the tool bar icons for the mask states or in the menu)- if you hide, disable and remove a mask... and then add another mask (later). It isn't obvious the mask is now associated with the IMAGE. Then, because you didn't think it worked you try again...... and again (but no change evident by looking at IMAGE which isn't active anyway by dragging another view to become a mask).

If creating one more graphical state to indicate an invisible (that is hidden and disabled mask) exists is undesirable- it might be nice to at least have the Process Console echo a mask has been applied, removed..etc. It isn't a process... but at least there is some indication something is going on. Looking at the mask states in the menu or icons does solve the problem... but it is subtle.

-adam

Offline pfile

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 4729
Re: Mask States
« Reply #1 on: 2017 October 06 08:58:44 »
i agree with what you are saying; i feel like if the user applies a new mask then it makes sense that the state should become enabled. this has bitten me many times and i've been using this software for almost 10 years now.

it might run counter to juan's philosophy for operations to have 'hidden' side effects though. also i wonder if coupling the applied and enabled states might mess up image histories or process containers and lead to different results when operations are done interactively vs. when done via process container.

rob


Offline ngc1535

  • PixInsight Old Hand
  • ****
  • Posts: 326
Re: Mask States
« Reply #2 on: 2017 October 06 09:05:18 »
Yeah... I understand (and I am certain the conversation about this has occurred before, but I could not easily find it).
I would seem to me that at least graphically indicating at all times a mask is associated (applied or not) with an image is an easier fix?
(I like my border of brown rather than filled brown idea). Of course... have no idea how difficult it would be to program this request.

-adam