DuetWifi driving me crazy
-
windows edge
-
Try using chrome or firefox. I haven't used windows edge but I know safari doesn't work well, and historically microsoft browsers are the worst in terms of supporting new features and frameworks.
-
But I just tried Firefox, I can now edit the config files with that and it saves them. Still can't see the gcodes file….
-
which is a step in the right direction, I can edit the configuration, just can't upload anything to print.
-
okay, found out what the problem was. The folder was named "gcodes-ormerod", apparently that is wrong and it must be just gcodes…. would love a slap forehead emoji right now...
-
can't tell my wife I have spent most of the day on this and it was a simple file name change…
-
I am glad you sorted it. For reference, you can find the required SD card folder structure here https://duet3d.com/wiki/SD_card_folder_structure.
-
The web interface should really support all browsers. This is 2016, not 1997.
-
The web interface should really support all browsers. This is 2016, not 1997.
It's not always possible. MS have never followed compliance. If all browsers were WebKit then 100% compliance could be achieved with ease.
-
I am glad you sorted it. For reference, you can find the required SD card folder structure here https://duet3d.com/wiki/SD_card_folder_structure.
yeah, I saw that, but figured that if the original files had the added tags that it would be allowed so I didn't think anything about it.
-
Web development requires testing. Not supporting or not testing with some of the major browsers shouldn't be considered acceptable.
-
tomasf, DuetWebControl is open source. I invite you to modify it to work around the failures of the so-called major browsers to implement the HTML 5 standard sufficiently. See https://html5test.com/compare/browser/mybrowser/edge-14/safari-9.1/chrome-52.html.
Edge browser is getting better, and almost all of DWC worked in it last time I tried it.
-
Web development requires testing. Not supporting or not testing with some of the major browsers shouldn't be considered acceptable.
MS Edge seems to have a ~5% market share spread across 3 versions:
https://www.netmarketshare.com/browser-market-share.aspx?qprid=2&qpcustomd=0
Not sure that can be considered "major"?
-
FYI The problem with editing config files is that Safari doesn't support the 'new File()' constructor used in upload.js (nor does IE or Edge). However it is supported in Chrome, Opera, and FireFox. See http://caniuse.com/#feat=fileapi
I've tried some of the usual work-arounds for this Safari issue, but not found one that works.
-
I have updated the Wiki to include a note on the folder naming, eca77 sorry you spent so much time on this!
https://duet3d.com/wiki/SD_card_folder_structureAlso added a note about browsers to here:
https://duet3d.com/wiki/Prerequisites_for_using_the_Duet_WiFiAnd this as a trouble shooting page:
https://duet3d.com/wiki/File_uploads_or_other_DWC_features_not_workingWhen any more information or workarounds for other browsers becomes available we can update the troubleshooting page.
-
FWIW I tried to find out why saving files in the System File Editor doesn't work in the latest version of Edge. With developer tools enabled, Edge pauses when I attempt to save the file as if an exception has occurred. But Edge is then completely unresponsive, denying me the possibility of finding out what the exception was. Microsoft needs to get its act together.
-
FWIW I tried to find out why saving files in the System File Editor doesn't work in the latest version of Edge. With developer tools enabled, Edge pauses when I attempt to save the file as if an exception has occurred. But Edge is then completely unresponsive, denying me the possibility of finding out what the exception was. Microsoft needs to get its act together.
Microsoft Edge 25.10586.0.0
MicrosoftEdgeHTML 13.10586Browser shows the following error in dev console:
[[language]] SCRIPT5002: Function expected dwc.js (47,165042)
This error points me to this line:
[c]var c=new File([d],a,{type:"application/octet-stream"}[/c]
-
Interesting, I am using the exact same version of Edge and it freezes on me every time, running under Windows 10 64-bit.
I guess the problem is lack of support for the File constructor as mentioned earlier.
-
This error points me to this line:
[c]var c=new File([d],a,{type:"application/octet-stream"}[/c]
Yes, this is as I posted above, the core problem is that Edge (and the other browsers) don't support the 'new File()' constructor.
You can sometimes work around this by using the 'new Blob()' constructor instead (A file is just a specific type of blob), but I couldn’t make that work here in a quick test. I'll try again.
-
Update, and good news! I just tested after a Safari update and the latest version of Safari supports the new File() constructor and thus the DWC file editor works in Safari 10.0.1 and later! (Won't work in any earlier versions)
Huzzah!
Not so for Edge or IE I'm afraid…
EDIT:
The following code may work in IE and Edge - I haven’t tested it in this case, but it's worked for me elsewhere:
Replace line 22 in upload.js
[c]var file = new File([content], filename, { type: "application/octet-stream" });[/c]With
[c]var file = new Blob([content], { type: "application/octet-stream" });
file.lastModifiedDate = new Date();
file.name = filename;[/c]Ideally this would only be done if the browser is detected as IE or Edge, or if new File() isn’t valid.