I am wondering if anybody noticed this kind of behavior. Especially that "apply" is grayed out is for me a strange thing.
And an additional question: is this congruent with the design guide lines for requesters?
This is simply a defect in the implementation, the 'Apply' button is unnecessary in this case as the form is modal and 'OK' will only dismiss the dialog if packaging is successful, it could be problematic if the dialog closed but packaging had failed.
We'll look at fixing it in a future release.
Also, would an option just to run packager with the existing options be useful, rather than always showing the dialog, which isn't changed that often?
Thanks for responding so quickly. I was wondering about the behavior, and now I know that my intuition was pointing towards something "odd" .
Now personally I am a big believer of not starting anything without first asking the user if he wants to keep some settings, just start the action or abort because he doesn't really want to do it right now.
Like I proposed in D11360 for Expedition, if you have such a button that would start packaging I would prefer to be asked the three possible questions:
1) Start package immediately (keeping current options)
2) Show the package dialog box (possibility to change options)
This would then together with the same behavior in Layout
1) Annotate immediately
2) Show the project integration requester
have a unification and a neat consistency of actions.
Let see how the other users comment on it.