That's not true, no where in the mock-up can you find "Realtime" !admin wrote:And you see the contradiction that is the source of the UI problem in jacky's mock-up: "Realtime" + "Refresh" button ...Either one or the other.
I think real time is a bad idea anyways, cause many patterns (batch, regexp, etc) don't make any sense anyways while they are being written/set, that's why I went with a "Refresh" button...The "fixed display" suggestion was not so bad but I don't like the doubling of info in one screen.j_c_hallgren wrote:And I, for one, was essentially interpreting "real time" as the ability to modify the pattern on same screen as results, and then be able to re-do the preview...not that the results would be constantly updating while I viewed them! So the 'refresh' button makes sense here.
Also, having some fixed display as to what pattern was used to create current results would be quite helpful while modifying it for another attempt, but not sure how best to do so, as my suggestion was turned down...
I didn't see this RTRP as just one screen, but rather as the 2nd screen of the two...so that one could avoid the back-and-forth between the two screens (should user not get it perfectly right the first time, or 'N'th time!) which I see as not ideal either. This is only for those that allow a settable pattern, as those that don't (URL escape, etc) wouldn't allow user to modify it anyway, so the RTRP would thus be the only screen in those cases, and would be slightly differently looking.admin wrote:This tells me: choosing a pattern and previewing the results are 2 operations that are better organized in 2 screens than in 1 screen.
Okay, and I do not see what's the problem with the current setup.j_c_hallgren wrote:I didn't see this RTRP as just one screen, but rather as the 2nd screen of the two...so that one could avoid the back-and-forth between the two screens (should user not get it perfectly right the first time, or 'N'th time!) which I see as not ideal either. This is only for those that allow a settable pattern, as those that don't (URL escape, etc) wouldn't allow user to modify it anyway, so the RTRP would thus be the only screen in those cases, and would be slightly differently looking.admin wrote:This tells me: choosing a pattern and previewing the results are 2 operations that are better organized in 2 screens than in 1 screen.
As I envison it, the initial screen is used to set the pattern, and user decides whether to do a preview or not, right? If preview done, then we go to RTRP screen, where we see results and get to tweak it...and IF we do, then we have to request a refresh (or decide to just go for it), which may cause a delay, just as doing a FileFind may on occasion...so what's the problem?
Maybe others see it differently, but that's how I would hope it ends up...
I find it quite natural! The necessity to open a new window elegantly reflects that there's work to be done. If you don't need the work, don't open the window. If you don't like the results go back to the interface to change the pattern.Me not so much... but this could be easily fixed by having Esc on the Preview window not close it (Cancel) but go back instead (Edit Pattern). That, would feel much more easy & natural to meadmin wrote:Okay, and I do not see what's the problem with the current setup.
I don't get itadmin wrote:The necessity to open a new window elegantly reflects that there's work to be done. If you don't need the work, don't open the window. If you don't like the results go back to the interface to change the pattern.
What do you mean by "If you don't need the work, don't open the window" ?? I would have thought it was what you previously said would become obsolete with RTRP : a third button to rename without bothering of a preview. 
Please do. Often do I use case changing or Url(Un)Escaping rename features, and I like them to be one-click actions. Having a preview to confirm me that "This" becomes "THIS" on uppercase just annoys me. It's not like like could have made a mistake in my regexp that would not work, or worse screw up the whole thing...admin wrote:INI Trick... I'll see...
I'll agree with "preview will just confirm what was likely expected", but not with the second sentence...In my case, it was not that complex, but just that it took a few tries to get what I wanted...and...ok, no...not frequent, but when used, it should be as user friendly as possible, IMO, and I believe that staying on preview screen (once there) is better.admin wrote:One should also remember that in most of the cases the preview will just confirm what you thought would happen anyway. And if the rename jobs are so complex and frequent that you find yourself hopping between 2 dialogs all day long: get a renamer software.
Yep, that's what I thought before, but I changed my mind. There will be a third button.jacky wrote:I don't get itadmin wrote:The necessity to open a new window elegantly reflects that there's work to be done. If you don't need the work, don't open the window. If you don't like the results go back to the interface to change the pattern.
Done.jacky wrote:I wish a third button "Rename" (aka without preview) would be added, with a KS like Ctrl+Enter, so it's easy to choose to use (Enter) or not (Ctrl+Enter) the preview
I think this should be a real config option, not just a tweak. But I'm not sure yet, how (to do it elegantly).jacky wrote:Please do. Often do I use case changing or Url(Un)Escaping rename features, and I like them to be one-click actions. Having a preview to confirm me that "This" becomes "THIS" on uppercase just annoys me. It's not like like could have made a mistake in my regexp that would not work, or worse screw up the whole thing...admin wrote:INI Trick... I'll see...
Yep, very good! Still, one thing: I would rename the button on preview, from "Cancel" to "Go back" or "Edit Pattern"admin wrote:Done.jacky wrote:I wish a third button "Rename" (aka without preview) would be added, with a KS like Ctrl+Enter, so it's easy to choose to use (Enter) or not (Ctrl+Enter) the preview
hmmm... ok. I'm not sure why someone would want a preview on those renames though, except MP3 ones, but let's say they wouldadmin wrote:I think this should be a real config option, not just a tweak. But I'm not sure yet, how (to do it elegantly).
Another (better?) possibility would be to decide on the fly because sometimes you want a preview, sometimes not -- and you don't want to change the config for this each time. A possibility would be sth like "hold Ctrl" while clicking the command to show a preview. But this conflicts with KS containing CTRL. Hmmm...
I'd be quite happy with a toggle option in the "Rename Special" menu, as "Auto-Refresh" in "View" menu is...this would apply to those options that normally are not previewed...and could be settable via KS also, but for us touchpad'rs would still be easily changeable....maybe call it "Preview All" or similar? Put it after a separator under MP3 so it's not in the way...admin wrote:I think this should be a real config option, not just a tweak. But I'm not sure yet, how (to do it elegantly).
Yep, that's it!j_c_hallgren wrote:I'd be quite happy with a toggle option in the "Rename Special" menu, as "Auto-Refresh" in "View" menu is...this would apply to those options that normally are not previewed...and could be settable via KS also, but for us touchpad'rs would still be easily changeable....maybe call it "Preview All" or similar? Put it after a separator under MP3 so it's not in the way...admin wrote:I think this should be a real config option, not just a tweak. But I'm not sure yet, how (to do it elegantly).
Uh, I just changed this back to 2 buttons because I was convinced by jacky. And I'm still convinced. "Cancel" refers to the preview, not to the rename. Makes it very easy to go back to edit the pattern. Press ESC 2 times to cancel the whole process. Not too much work, or?j_c_hallgren wrote:I'd also have three buttons on preview: "Rename Now ; Edit Pattern ; Cancel"
as those are the three possible choices I'd want to make at this point...and right now, I don't see a one-click way to abandon the Rename totally...
Well, I'm still of the opinion that having 'Cancel' on preview implies bail-out so having it be 'Edit Pattern' makes it 100% clear that one can't bail-out directly that way...or have it be 'Cancel Preview'? Yes, I understand. Your opinion would be different, I guess, if the Preview dialog would be on top of the Edit Pattern dialog (instead of replacing it), and it should be on top of it! The only reason why it is not: it would cost me a full day to rearrange the code to accomplish this. No time right now for this...j_c_hallgren wrote:
admin wrote:Yes, I understand. Your opinion would be different, I guess, if the Preview dialog would be on top of the Edit Pattern dialog (instead of replacing it), and it should be on top of it!j_c_hallgren wrote:
I didn't realize it until you wrote this, but yes , that is true! If the preview were a subset panel to Rename, then Cancel would be more obvious that it goes back to higher/prior panel, but as they are same level panels, then Cancel implies bail-out, IMHO.Three buttons would be a simpler coding change and still would allow users to easily decide the equivalant of "Back","Next","Exit" and would allow a quick bail-out if desired (which a subset panel would not!)admin wrote:So, I'm undecided. I'm willing to go back to my first version with three buttons
Edit Pattern | Rename Now (default) | Cancel
but I would like some more opinions. Or better: experience of usage. Get renaming, folks!
XYplorer Beta Club