Search This Blog
Wednesday, March 25, 2015
Save & Close again: To close, or not to close: that is the question - YOUR FEEDBACK IS NEEDED!
Just a quick help request to you, guys...
There was one point regarding the behavior described in my recent post at
Corrected Save & Close Action behavior on the Web in v15.1, which we were not very sure about:
#2. If the DetailView was first opened in the View mode from a root ListView, then switched to the Edit mode by an end-user via the Edit Action, then Save & Close will save the changes and return you back to the View mode instead of closing and showing the source ListView.
We received only a couple of comments on this very point and since this change is not very important to us, we wanted to make sure the new behavior meets the needs of the most users. So, I would kindly ask you take a minute to leave a comment to my blog post on the desired behavior you would like to see in this situation. Thank you in advance!
P.S.
I personally tend to think that this should be a real "close" result = navigating back to the ListView regardless the DetailView was in the View mode before or not. But you may disagree and consider this as navigating back to the previous view state in the stack...who knows...
There was one point regarding the behavior described in my recent post at
Corrected Save & Close Action behavior on the Web in v15.1, which we were not very sure about:
#2. If the DetailView was first opened in the View mode from a root ListView, then switched to the Edit mode by an end-user via the Edit Action, then Save & Close will save the changes and return you back to the View mode instead of closing and showing the source ListView.
We received only a couple of comments on this very point and since this change is not very important to us, we wanted to make sure the new behavior meets the needs of the most users. So, I would kindly ask you take a minute to leave a comment to my blog post on the desired behavior you would like to see in this situation. Thank you in advance!
P.S.
I personally tend to think that this should be a real "close" result = navigating back to the ListView regardless the DetailView was in the View mode before or not. But you may disagree and consider this as navigating back to the previous view state in the stack...who knows...
Subscribe to:
Post Comments (Atom)
Hello,
ReplyDeleteI agree with Your P.S.
I also want this should be a real 'close'.
Thanks.
Hi
ReplyDeleteThat is good idea return to ListView
I agree with real close.
ReplyDeleteA close action that does not close the window makes no sense.
Real close would be nice!
ReplyDeleteReal close
ReplyDeleteI agree, return to the listview
ReplyDeleteReal close is preferred.
ReplyDeleteReal close please
ReplyDeleteReal close please
ReplyDelete+1 for Real Close
ReplyDeleteReal Close might be the best way to go as you will actually do what the actions says
ReplyDeleteFrom James Makumbi (posted on LinkedIn):
ReplyDelete"Yeah, I was doing a customer demo and having to close then look for list view was tiresome. It needs to close to listview. There is something natural about it that way."
Hi,
ReplyDeletefor me, the element opening must be a DetailView element in edit mode, and close to Listview, like as winforms
Real close to the list view is essentially ideal.
ReplyDeleteReal close to the list view is essentially ideal.
ReplyDeleteI greatly appreciate your input, guys. We've changed the point #2 as suggested (= real close).
ReplyDeleteMaybe a real close looks ideal, sometimes it's needed to return to view mode, especially when you edit in web app, when trying to show that record in report.
ReplyDeleteIt's more useful&faster to make changes and return to view mode and take the report.
Thanks for describing your scenario, Onur. It is possible to accomplish what you want by writing a few code lines as per https://documentation.devexpress.com/#eXpressAppFramework/DevExpressExpressAppWebSystemModuleWebModificationsController_QueryCloseAfterSavetopic
Delete