XYcopy Taskbar visible -- What is the theory?

[Zardoz2293]

I'm noticing the XYcopy.exe process listed in the Taskbar in addition to XY. Curious as to the theory as to why it's displayed during the custom copy.

What are your thoughts?

[Twisten]

Well its a separate process and you're more than likely have it set to keep the window open once a custom copy operation was done, so having it on the taskbar would keep you from forgetting to close it for once.

[Zardoz2293]

Why would you want to keep the custom copy dialog displayed when once it was finished? Assuming of course the task was successfully achieved.

I'm just asking. I'm not for it and not against it.

Since it's a separate process you'd have to add some extra plumbing to get it displayed to the foreground if someone click on XY (as to make it behave as if it's a single integrated app) and hence the Taskbar. What happens if you do "Move intra-volume (runs at once in parallel process)" and you move one-hundred billion folders, do you get more than one XYcopy dialog or more than on app icon in the Taskbar?

In regards to the queued processing, is it intelligent asynchronous queuing? If you have single physical drive volumes:
(Copy #1) thing_1 at Source: "C:" to Target "D:"; (Copy #2) thing_2 at Source: "C:" to Target "D:" -- You need asynchronous activity.

However,
(Copy #1) thing_3 at Source: "C:" to Target "D:"; (Copy #2) thing_4 at Source: "E:" to Target "F:" -- You can do synchronous processing without knowing it.

[nas8e9]

Why would you want to keep the custom copy dialog displayed when once it was finished? Assuming of course the task was successfully achieved.

I'm just asking. I'm not for it and not against it.

XYcopy can show reports upon task completion, if you mean why XYcopy can be set to remain open.

As for why XYcopy.exe came about: VB 6 doesn't offer multithreading that actually works, unfortunately, meaning potentially long-running file operations had to be taken out-of-process.

Since it's a separate process you'd have to add some extra plumbing to get it displayed to the foreground if someone click on XY (as to make it behave as if it's a single integrated app) and hence the Taskbar.

I prefer the "detached" arrangement as, especially when combined with queuing, XYplorer remains fully available. As for status display, the Background Jobs button in the status bar conveys that something is happening.

For the Windows 7-crowd, a nice planned addition is to have the XYcopy taskbar icon show progress like the Windows Shell progress dialogs do.

What happens if you do "Move intra-volume (runs at once in parallel process)" and you move one-hundred billion folders, do you get more than one XYcopy dialog or more than on app icon in the Taskbar?

Do you have a screenshot?

In regards to the queued processing, is it intelligent asynchronous queuing? If you have single physical drive volumes:
(Copy #1) thing_1 at Source: "C:" to Target "D:"; (Copy #2) thing_2 at Source: "C:" to Target "D:" -- You need asynchronous activity.

However,
(Copy #1) thing_3 at Source: "C:" to Target "D:"; (Copy #2) thing_4 at Source: "E:" to Target "F:" -- You can do synchronous processing without knowing it.

This has been suggested; I think it's on Don's list somewhere as target intelligence.

[Zardoz2293]

XYcopy can show reports upon task completion, if you mean why XYcopy can be set to remain open.

As for why XYcopy.exe came about: VB 6 doesn't offer multithreading that actually works, unfortunately, meaning potentially long-running file operations had to be taken out-of-process.

Why would you want to keep the dialog open upon successful copy. VB6 = Mutex; You can also write true services too.

I prefer the "detached" arrangement as, especially when combined with queuing, XYplorer remains fully available. As for status display, the Background Jobs button in the status bar conveys that something is happening.

For the Windows 7-crowd, a nice planned addition is to have the XYcopy taskbar icon show progress like the Windows Shell progress dialogs do.

XY being fully available has nothing to do with "detached" arrangement (as in dialog). Doesn't the icon in the Taskbar perform the action of the "status display"? So you'd group XYplorer and XYcopy for the Aero Taskbar Effect?

Do you have a screenshot?

I was hoping you did or a video, otherwise I'd be required to run my own test to get the answer.

This has been suggested; I think it's on Don's list somewhere as target intelligence.

What about synchronous processing of:
(Copy #1) thing_5 at Source: "C:" to Target "D:"; (Copy #2) thing_6 at Source: "C:" to Target "E:" -- You can synchronous processing two dissimilar reads without knowing it and write to two different targets.

///

What about ultra-fast random synchronous read-write activity to create the next version of XY which was dictated through Yoda Speak with logic provided by Online Magic Eight Ball?

Totally unrelated to this thread, including the complete fallacy above, is this useful little gem: Mouse Scroll Wheel + Control for Tree, List and Catalog font point size change -- a very nice touch.

[nas8e9]

Why would you want to keep the dialog open upon successful copy. VB6 = Mutex; You can also write true services too.

I'm confused: I take it you mean the Custom Copy dialog rather than the Windows Shell one? If so, Configuration > File Operations > Custom Copy Operations > Configure > Keep progress dialog open, allows you the option.

I prefer the "detached" arrangement as, especially when combined with queuing, XYplorer remains fully available. As for status display, the Background Jobs button in the status bar conveys that something is happening.

For the Windows 7-crowd, a nice planned addition is to have the XYcopy taskbar icon show progress like the Windows Shell progress dialogs do.

XY being fully available has nothing to do with "detached" arrangement (as in dialog). Doesn't the icon in the Taskbar perform the action of the "status display"? So you'd group XYplorer and XYcopy for the Aero Taskbar Effect?

I thought you suggested to have the XYcopy-window modal to XYplorer's main window, which would negate the advantage XYplorer offers: XYplorer remaining available.

I do agree that, on Windows 7 and later, XYplorer and XYcopy's icons being grouped with the latter gaining progress display, will be very nice to have once we reach those items on the roadmap.

This has been suggested; I think it's on Don's list somewhere as target intelligence.

What about synchronous processing of:
(Copy #1) thing_5 at Source: "C:" to Target "D:"; (Copy #2) thing_6 at Source: "C:" to Target "E:" -- You can synchronous processing two dissimilar reads without knowing it and write to two different targets.

No disagreement there; once XYcopy 3.0 comes along, it should be included. Unfortunately, going by the roadmap (plus the localisation work coming up) that won't be soon.

[Zardoz2293]

I'm confused: I take it you mean the Custom Copy dialog rather than the Windows Shell one? If so, Configuration > File Operations > Custom Copy Operations > Configure > Keep progress dialog open, allows you the option.

Yes, I know. The question was why would you want to keep the dialog displayed when finished if the copy was successful? If you like it great, but I would like to know why you like it.

I thought you suggested to have the XYcopy-window modal to XYplorer's main window, which would negate the advantage XYplorer offers: XYplorer remaining available.

I do agree that, on Windows 7 and later, XYplorer and XYcopy's icons being grouped with the latter gaining progress display, will be very nice to have once we reach those items on the roadmap.

I'm pretty much an anti-modal kind of guy. You could have the custom copy thingy within XY visually and it could be completely out-of-process, fluid, etc. My perspective is the tool is always available and responsive regardless of activity. BTW, where is that road map posted? I saw it once. In the Lounge?

What do you think localization is going to do to the agile development cycle, once implemented?

[nas8e9]

I'm confused: I take it you mean the Custom Copy dialog rather than the Windows Shell one? If so, Configuration > File Operations > Custom Copy Operations > Configure > Keep progress dialog open, allows you the option.

Yes, I know. The question was why would you want to keep the dialog displayed when finished if the copy was successful? If you like it great, but I would like to know why you like it.

I don't . Especially for people with long-running (network) jobs however, it can be reassuring I guess, especially when combined with the Report option.

I thought you suggested to have the XYcopy-window modal to XYplorer's main window, which would negate the advantage XYplorer offers: XYplorer remaining available.

I do agree that, on Windows 7 and later, XYplorer and XYcopy's icons being grouped with the latter gaining progress display, will be very nice to have once we reach those items on the roadmap.

I'm pretty much an anti-modal kind of guy. You could have the custom copy thingy within XY visually and it could be completely out-of-process, fluid, etc. My perspective is the tool is always available and responsive regardless of activity.

I agree that would be ideal. Unfortunately and with the admission I'm outside my competence here, but fluent IPC communication in combination with XYplorer.exe both listening and showing a high-precision UI, may make for performance problems.

BTW, where is that road map posted? I saw it once. In the Lounge?

It's located here. The usual disclaimers are that there are no guarantees with regard to order and speed, and basically Don can change his mind at any time. Also, it's a high-level overview only.

What do you think localization is going to do to the agile development cycle, once implemented?

Wrong guy to ask . My impression is that, once the initial work is done, Don will return to his current way of working, with the translators left to catch up. Any UI text additions will of course, need some additional sizing. Fortunately German (Don's native language) seems to take the most space, so...

Additionally, there will be overhead for Don when prepping a release. I think he said he'd only do that for releases however, with betas remaining English-only.