XYplorer Beta Club

admin wrote:Too much for me at the moment.

I understand.

admin wrote:But can you dump the clipboard after you copied a folder to it? Simply save a CLP file (you can do this from C:\WINDOWS\system32\clipbrd.exe) and send it to me by email. I might be able to see something in it.

On LAN (Win XP box) the copy operation has no issues (can be pasted to LOCAL by using WE on LOCAL, or to the same LAN using XYP). The clipboard on LAN does show the directory, naturally.

On TARGET (Win7 box) - no clipbrd.exe, had to copy (per forum recommendation) the clipbrd.exe from the Win XP Box. Nothing is shown in it.

As a reference, I just tested Zabkat's xplorer2 Lite to see how other non-Windows file managers handle this directory copy - it did this OK. However, I have no idea if that program manages its buffers by itself or relegates it to Windows routines.

Anyway, thanks for the effort trying to resolve this issue.
I will email you the .clp file from the copy operation on LAN.

CLP file was emailed.

Oh, one request if I may:
To have the option on the error message to terminate the paste operation - right now if I make the mistake and try to paste into XYP and not into WE, I have to dismiss the error message as many times as there are files in the copied sub-directory - very annoying when one has 10+ files there...

Kob wrote:CLP file was emailed.

Oh, one request if I may:
To have the option on the error message to terminate the paste operation - right now if I make the mistake and try to paste into XYP and not into WE, I have to dismiss the error message as many times as there are files in the copied sub-directory - very annoying when one has 10+ files there...

Thanks, I opened the file from clipbrd.exe and surprisingly I could read it in XY without problem. "E:\Kill" was correctly (? yes ?) detected as being present in the clipboard. Hm.

Request: Should work better in next version.

Well, I am not surprised that you could read the clipboard - as you specifically requested, and I confirmed in "I will email you the .clp file from the copy operation on LAN" , the clipboard content on LAN should be fine since I can paste its content on LOCAL in WE. It is the clipboard content transfer through VNC to XYP that somehow messes things up...

Kob wrote:Well, I am not surprised that you could read the clipboard - as you specifically requested, and I confirmed in "I will email you the .clp file from the copy operation on LAN" , the clipboard content on LAN should be fine since I can paste its content on LOCAL in WE. It is the clipboard content transfer through VNC to XYP that somehow messes things up...

Clipboard content transfer through VNC... hmm... I'd say clipboard is clipboard. If you mailed me the clipboard contents that XY cannot read on your system I have no explanation for it because XY can rread them on my system.

Is it too simple to say:
WE and XY can "read" clipboard.
WE can copy it, XY can not?

But the clipboard is, as I understand, a result of paste from VNC. Is this really full compatible with other copies (from LAN), or might there be a difference?

PeterH wrote:Is it too simple to say:
WE and XY can "read" clipboard.
WE can copy it, XY can not?

But the clipboard is, as I understand, a result of paste from VNC. Is this really full compatible with other copies (from LAN), or might there be a difference?

From XY's point of view, (when pasting) the clipboard is a local source of information. Either it can read it or not. I still have not seen clipboard contents that XY cannot read. So I cannot investigate what's the problem.

admin wrote:

PeterH wrote:Is it too simple to say:
WE and XY can "read" clipboard.
WE can copy it, XY can not?

But the clipboard is, as I understand, a result of paste from VNC. Is this really full compatible with other copies (from LAN), or might there be a difference?

From XY's point of view, (when pasting) the clipboard is a local source of information. Either it can read it or not. I still have not seen clipboard contents that XY cannot read. So I cannot investigate what's the problem.

Sorry, excuse me, I don't know too much about this - but just want to ask:

When you say "read clipboard" - what do you mean: reading data in the clipboard, or reading data refered to by clipboard? I can imagine a situation where you can read the clipboard, but not what it's referring to?
(Maybe this is rubbish - maybe not...)

PeterH wrote:

admin wrote:

PeterH wrote:Is it too simple to say:
WE and XY can "read" clipboard.
WE can copy it, XY can not?

But the clipboard is, as I understand, a result of paste from VNC. Is this really full compatible with other copies (from LAN), or might there be a difference?

From XY's point of view, (when pasting) the clipboard is a local source of information. Either it can read it or not. I still have not seen clipboard contents that XY cannot read. So I cannot investigate what's the problem.

Sorry, excuse me, I don't know too much about this - but just want to ask:

When you say "read clipboard" - what do you mean: reading data in the clipboard, or reading data refered to by clipboard? I can imagine a situation where you can read the clipboard, but not what it's referring to?
(Maybe this is rubbish - maybe not...)

No rubbish, this is absolutely possible. But in this case here, the clipboard cannot even be read (at least that's what I hear from the OP).