XYcopy - AutoQueue

[Mesh]

Yep, just need a cool idea for the icon...

[admin]

Yep, but this is exactly how the setting works anyway. It controls whether the currently triggered operation (if another one is being processed) is pushed on the queue or executed immediately.

Ah. Well, in that case, it should be a piece of cake to implement.

"Auto-queue pending file operations" is probably a misleading name for it. Now that you know exactly what it does, do you have a better suggestion? "If file operations are being processed in the background then push new file operations on the queue" is a bit long. Can you say it in 5 words?

[Mesh]

"Auto-queue pending file operations" is probably a misleading name for it. Now that you know exactly what it does, do you have a better suggestion? "If file operations are being processed in the background then push new file operations on the queue" is a bit long. Can you say it in 5 words?

"Queue file operations" seems relatively straighforward. If enabled, file ops (except deletes, and same-drive moves) will be added to the queue. If disabled, they won't.

The exceptions noted above can be explained in the Config box and in the tooltip for the button.

[admin]

"Auto-queue pending file operations" is probably a misleading name for it. Now that you know exactly what it does, do you have a better suggestion? "If file operations are being processed in the background then push new file operations on the queue" is a bit long. Can you say it in 5 words?

"Queue file operations" seems relatively straighforward. If enabled, file ops (except deletes, and same-drive moves) will be added to the queue. If disabled, they won't.

The exceptions noted above can be explained in the Config box and in the tooltip for the button.

Cool, thanks.

[zer0]

I attach screenshot of the menu. All yellow items are sent to background/queue if background/queue are enabled. ("Backup Here" will follow in XYcopy 2.0) How would you modify this menu?

If it's not too late I'd like to suggest potential modifications of this menu, as follows:

1) Refactor the "Move Here with/As.../to..." into a pull-out menu of "Move Here". Same for "Copy Here".
2) Is "Cancel" needed?
3) Remove "Here" from the "Create..." menu items.
4) No need for ellipsis in "Shell Context Menu...".
5) Substitute "Today" for "Now".

[TheQwerty]

3) Remove "Here" from the "Create..." menu items.

Why should it be removed from the Create items but not the other ones? They should be consistent in this.

5) Substitute "Today" for "Now".

I agree the wording is off but using Today would be incorrect since the template may define the use of the time in the suffix. Ideally it should show the actual values that would be used for the suffix, but as the Date Mod. and Number will be different for every item in the operation it may look odd to only do it for the current date/time.

To be honest I almost think it makes most sense to replace the suffix items with a new item "blah Here with Suffix..." which opens a dialog similar to the Move/Copy/Backup or Rename dialogs that allows the user to define/modify the suffix.

Pros:
-Cleaner menus
-More control over the suffix used.
-Eliminates much of the need to make these 'blah Here' sub-menus.

Cons:
-An increase in the number of steps in user's workflow.

That said I would think most users end up using the same suffix for most tasks so it's probably only one additional click. If it bothered them that much they could script it to avoid the dialog or Don could add a dynamic menu item "blah Here with Suffix [last used]". The latter would remove some of the benefit but I still think it's an improvement (plus it doesn't need to be added until two fools wish. )

[jacky]

If it's not too late I'd like to suggest potential modifications of this menu, as follows:

1) Refactor the "Move Here with/As.../to..." into a pull-out menu of "Move Here". Same for "Copy Here".
2) Is "Cancel" needed?
3) Remove "Here" from the "Create..." menu items.
4) No need for ellipsis in "Shell Context Menu...".
5) Substitute "Today" for "Now".

I'd vote no to all of those (except maybe 1, but I'm not sure a submenu wouldn't just slow things down for now... so still a no).

--

Hi,

I'm jacky & I haven't been active lately over here but I still use XY every day, loving it*, and having dome some little test with the recent XYcopy I thought I'd share a few remarks. I know you guys don't like long list of requests for a first post, but this is only my first post in a while, so bear with me, please

* : Off topic, but I'm happy you re-introduced the "Empty Recycle Bin" thing. On one computer I use daily (which still has a somewhat pretty old version of XY ATM) I use that one many times a day every day! Thanks for that (extended to all those who fought for it).

- I'll try not to repeat (too much of) what's been said before.

- I know some way to turn on/off the queue as been discussed. Good, it's a must-have. I also think on some "features" a way to enable/disable queue for this one operation only would be a good thing. For instance, scripting commands should of course have an extra param added. Also the M/C/B To window GUI could have a checkbox, reflecting the default/global option but allowing one to change that option for that one operation only.
I also think it might be good on that right-d&d menu. Could you add an option in there? A menu-item one could check/uncheck (upon clicking it its state/checkmark would switch, then the menu be re-shown right away) before starting the actual operation...

- From my (quick) testings, some features ignore the queue completely. Namely the Ctrl+S/D/etc (Save Here As & co) didn't want to queue stuff, ever. That's just not-yet-done, right?

- I strongly believe you need to give us a GUI for the queue. I'm not sure if that was the suggestion when the screenshot from Opera showed up (on a related note: IMO it would be better if you closed one of those topics, to centralize everything XYcopy in one single place. Easier that way to read everything/follow stuff/avoid dupes I think...), but something so one can see what's queued, remove a job from the queue, change its properties maybe (from copy to move, change destination, ...), or move it up/down (re-arrange priority/order of jobs), pause stuff, etc

- I possibly noticed other stuff/had other ideas, but I'm blank right now or they've been addressed before. And I'm too excited to be posting here again to wait so here I go...

[zer0]

If it's not too late I'd like to suggest potential modifications of this menu, as follows:

1) Refactor the "Move Here with/As.../to..." into a pull-out menu of "Move Here". Same for "Copy Here".
2) Is "Cancel" needed?
3) Remove "Here" from the "Create..." menu items.
4) No need for ellipsis in "Shell Context Menu...".
5) Substitute "Today" for "Now".

I'd vote no to all of those (except maybe 1, but I'm not sure a submenu wouldn't just slow things down for now... so still a no).

If people have the need for speed they may assign a CTB/UDC Pull-out context menus are not a novelty in XYplorer and they are present to group common menu items under one hood. As for semantics of text labels, I'm prepared to fight tooth and nail for those

[j_c_hallgren]

3) Remove "Here" from the "Create..." menu items.

Why should it be removed from the Create items but not the other ones? They should be consistent in this.

5) Substitute "Today" for "Now".

I agree the wording is off but using Today would be incorrect since the template may define the use of the time in the suffix.

To be honest I almost think it makes most sense to replace the suffix items with a new item "blah Here with Suffix..." which opens a dialog similar to the Move/Copy/Backup or Rename dialogs that allows the user to define/modify the suffix.

I'm with TheQwerty on this (almost)...

1) I don't agree that a dialog (I'm saying panel type thing) would be best, but a sub-menu for the suffixed items would make sense...it would add one more click but would make accessing other items on main submenu easier and would also allow more "suffix with" items to be added it desired.
2) Yes, "cancel" is needed! It's available on WE context and serves as way to abort using only mouse/TP.
3) Given that WE and other FM's use the "here", we should also as that appears to be standard..
4) My favorite "..." could be removed as that is somewhat unneeded.
5) Agree with TheQwerty here also..

jacky: Welcome back! Where the heck have you been hiding? It hasn't been the same around here without ya, and sadly the wiki is getting a bit dated and I've not had the ability to help it much either (due to eyesight issues which also has kept my blog a bit behind)...

[phatmankerr]

Just out of interest and apologies if this is already implemented / been mentioned.

Are we going to be able to view a list of queued items anywhere?

I noticed the items were appearing in the status bar - which seemed sensible - but disappeared if you carried out any other operation - and I couldn't find a way to see a list of queued items (a tooltip on a ' status bar item that was present as long as there were queued items would seem like a nice clean way of doing it).

Alternatively are we going to have a full dialog as per undo/redo?

I can see this being another one of XY's super useful features - kudos Don

Apologies I wrote the above offline when this thread had just started - And I didn't check before posting (was being hassled by the boss) - the whole thread is a discussion of the best options re. what I asked - ignore my stupidity.

[admin]

Just out of interest and apologies if this is already implemented / been mentioned.

Are we going to be able to view a list of queued items anywhere?

I noticed the items were appearing in the status bar - which seemed sensible - but disappeared if you carried out any other operation - and I couldn't find a way to see a list of queued items (a tooltip on a ' status bar item that was present as long as there were queued items would seem like a nice clean way of doing it).

Alternatively are we going to have a full dialog as per undo/redo?

I can see this being another one of XY's super useful features - kudos Don

Apologies I wrote the above offline when this thread had just started - And I didn't check before posting (was being hassled by the boss) - the whole thread is a discussion of the best options re. what I asked - ignore my stupidity.

It happens that I added exactly this some hours ago...

[Mesh]

Okay, I just grabed v8.90.0006. I haven't had the time to do any real testing yet, but I did want to note that the Status Log really needs to have the time a job executed, in addition to the time it was added.

Eventually, the Status Log should be part of the file op dialog box, but until you write your own API, this will work. I assume the ability to control live jobs will come later.

On a small side note, I can't say I'm fond of the Queue toolbar icon.


But in any case, thanks for continuing to improve this.

[zer0]

2) Yes, "cancel" is needed! It's available on WE context and serves as way to abort using only mouse/TP.
3) Given that WE and other FM's use the "here", we should also as that appears to be standard..
5) Agree with TheQwerty here also..

2) Really? Neither white space nor file context menu in WE (on XP) feature "Cancel". Also, what would you be aborting?
3) Once again, on XP, neither of WE's context menus shows any sign of "here"...
5) Then "Today/Now" would suffice to cater for a pre-defined template. Asking for a dialogue window for each such operation is a bit over the top.

[admin]

If it's not too late I'd like to suggest potential modifications of this menu, as follows:

1) Refactor the "Move Here with/As.../to..." into a pull-out menu of "Move Here". Same for "Copy Here".
2) Is "Cancel" needed?
3) Remove "Here" from the "Create..." menu items.
4) No need for ellipsis in "Shell Context Menu...".
5) Substitute "Today" for "Now".

I'd vote no to all of those (except maybe 1, but I'm not sure a submenu wouldn't just slow things down for now... so still a no).

--

Hi,

I'm jacky & I haven't been active lately over here but I still use XY every day, loving it*, and having dome some little test with the recent XYcopy I thought I'd share a few remarks. I know you guys don't like long list of requests for a first post, but this is only my first post in a while, so bear with me, please

* : Off topic, but I'm happy you re-introduced the "Empty Recycle Bin" thing. On one computer I use daily (which still has a somewhat pretty old version of XY ATM) I use that one many times a day every day! Thanks for that (extended to all those who fought for it).

- I'll try not to repeat (too much of) what's been said before.

1 - I know some way to turn on/off the queue as been discussed. Good, it's a must-have. I also think on some "features" a way to enable/disable queue for this one operation only would be a good thing. For instance, scripting commands should of course have an extra param added. Also the M/C/B To window GUI could have a checkbox, reflecting the default/global option but allowing one to change that option for that one operation only.
I also think it might be good on that right-d&d menu. Could you add an option in there? A menu-item one could check/uncheck (upon clicking it its state/checkmark would switch, then the menu be re-shown right away) before starting the actual operation...

2 - From my (quick) testings, some features ignore the queue completely. Namely the Ctrl+S/D/etc (Save Here As & co) didn't want to queue stuff, ever. That's just not-yet-done, right?

3 - I strongly believe you need to give us a GUI for the queue. I'm not sure if that was the suggestion when the screenshot from Opera showed up (on a related note: IMO it would be better if you closed one of those topics, to centralize everything XYcopy in one single place. Easier that way to read everything/follow stuff/avoid dupes I think...), but something so one can see what's queued, remove a job from the queue, change its properties maybe (from copy to move, change destination, ...), or move it up/down (re-arrange priority/order of jobs), pause stuff, etc

- I possibly noticed other stuff/had other ideas, but I'm blank right now or they've been addressed before. And I'm too excited to be posting here again to wait so here I go...

Welcome back. (Oh god, this means work's getting tough again for me... )

1 - This is for XYcopy 2.0. Currently all jobs will have to obey to the global settings.
2 - Yep, will add today.
3 - Again, XYcopy 2.0 (if at all, I find it partly a bit over the top). Although I will work a bit on the current first version of the Status Log.

Re the menu reorganization suggestion: No, thanks. I think it's fine as it is.

[admin]

I hereby close this topic.

More XYcopy wishes please here:
http://www.xyplorer.com/xyfc/viewtopic.php?f=5&t=4784