Thanks for this amazing program Qazhax! Hower, i tried running the client today but i can't seem to login through it either normal means (Which i assume is because doodleordie's https certificate isn't set-up properly) or through the cookie. When i try the cookie login, screen just flashes and it goes back to the login screen. Is there some update with the JRE that's maybe screwing something up? Or did they change something with the doodleordies website? (Which i assume is unlikely) I am using windows 10 with jre-8u261.
Viewing post in Bug reports
The site recently switched to a full https site, which is causing this. Earlier only the login page was using https, so it was possible to just go around the login page when the certificate is expired, but now the cert expiring just breaks the entire client. And the cert expired last Thursday. I don't have access to any of the server things so I can't fix it on my own. I suppose I should try to notify the admins as soon as possible when sth breaks on the server side.. I'll try to change the error messages to reflect the change when I have time.
That's a great idea, thanks!
The more complex save files often get over a megabyte in size and trying to paste the save data to the browser directly would likely be pretty slow. When I last tried playing around with the saves on site I could freeze the browser trying to access the saves, but that was years ago and directly from the localstorage tab in the inspector. The save/load script I made (possibly the same you're talking about) accesses the localstorage from javascript and doesn't seem to lag much at all, so making a function that could load save data from the client shouldn't be impossible. I'll try if I can make a js script that could load the contents of a text file into the localstorage, that should make it possible to load doodles from the client.
The client technically can produce save files that the site can read, but the functionality is not linked to any button, so I'll have to add some keybind to save the doodles in that format once I get the javascript working.
edit: I got the javascript mostly working but it's late so I'll continue later.
The workaround now mostly works, but it induces a few limitations on the doodles. The colours in the browser saves are saved as the #aabbcc form, but without the first #, so it's not possible to export semitransparent lines. The save format is also unable to save numbers beyond [0,520] so the locations to up, left and right of the canvas get squished back inside the canvas, the lines going below the bottom of the canvas aren't affected as they are still inside the range.
I'll check if I can automatically cut off the parts of the lines outside the canvas and post the workaround a bit later once I've eaten and stuff.
The dod browser format saves are also unable to use higher accuracy than 0.5. adding a file with filename "config" and contents "accuracy=2" will make the client use the same accuracy to help avoid drawing too detailed and having it get destroyed in the conversion.
The browser script for loading the file contents to localstorage is available at http://qazhax.herp.io/scripts/. I uploaded a new version of the client here, in the new version ctrl+shift+s saves in the browser format. The saved file can then be dragged and dropped onto the popup created by the browser script and the script will load it into the active room.
I also finally changed the error messages while I was at it.
Very cool stuff. Thank you for your work Qaz! Edit: I'm a bit confused by the Config thing, i assume you mean either a .txt file or a regular file with no extension with the accuracy=2 but when launching and going into offline mode the whole app crashes, not sure if it's just me missing something or not
The config file should not cause any crashes no matter what it contains. The filename it's looking for is just "config" without an extension or the quotes. I recently added support for pen pressure and that requires the files "libjpen-2-3.jnilib" and "jpen-2-3-64.dll" that should be included in the zip to be in the same folder as the .jar file or it might crash. I'll look into this later.