Duet Web Control 2.0.0-RC5

AlexLin

@chrishamm Today I had no problems with the refreshing of the height map...keep my fingers crossed

garyd9

Ummm.. perhaps a stupid question, but with DWC2 (RC5), how do I copy gcode files from one directory to another?

In DWC1, I could just drag them and drop them into the destination folder (or to a parent folder if I drop the file on the breadcrumb.) When I try to do the same with DWC2RC5, the mouse cursor turns into a circle with a line through it (indicating something that isn't allowed.)

This is especially annoying when used with a slicer that uploads gcode files to the root g-code directory of the duet...

(My current work-around is to force DWC1 when I need to move files around.)

chrishamm

@garyd9 said in Duet Web Control 2.0.0-RC5:

Ummm.. perhaps a stupid question, but with DWC2 (RC5), how do I copy gcode files from one directory to another?

In DWC1, I could just drag them and drop them into the destination folder (or to a parent folder if I drop the file on the breadcrumb.) When I try to do the same with DWC2RC5, the mouse cursor turns into a circle with a line through it (indicating something that isn't allowed.)

This is especially annoying when used with a slicer that uploads gcode files to the root g-code directory of the duet...

(My current work-around is to force DWC1 when I need to move files around.)

Thank you for your report, it looks like drag&drop was no longer working in Chrome-based browsers due to "security reasons". Apparently Chrome does not allow reading user payloads from the object being dragged whereas Firefox allows this. It's been fixed in RC6.

wilriker

@garyd9 said in Duet Web Control 2.0.0-RC5:

This is especially annoying when used with a slicer that uploads gcode files to the root g-code directory of the duet...

Don't know which slicer you use but when uploading through Cura RRF plugin you can specify the path it should end up by simply adding it to the file name, e.g. instead of just using sliced_object.gcode change it to path/it/should/go/sliced_object.gcode.

This might also work for other upload plugins. I am not sure though if the path has to exist or not (I think it will be created if missing).

fma

It also works from Slic3rPE (the version I have fails if using spaces, but it may have been fixed in latest releases).
I think missing dirs are created.

kraegar

I think I've figured out why sometimes the ability to navigate up one directory is missing. If you're in a subdirectory and lose connection (say, due to powering off), when I reconnect it displays the file list for that sub directory I was in previously, but then when I try to print one it says that file isn't found, but is listing the main gcode directory, not the subdirectory for the file list it's displaying. There is no ability to move up one directory (because it already thinks I'm at the "root". If I refresh, it takes me back to my main gcode directory, and I can then navigate around normally.

chrishamm

@kraegar Yep, I think that has been fixed in RC6.