Will it risk my computer?
Printable View
Will it risk my computer?
Nope. You provide the IP address of the printer and the name of the file. The tool searches for printers, and if it doesn't find one that matches the specified IP, then well, it won't work. If the file doesn't exist, Hmmm.. not sure about that, it may try to open and send. I haven't tried that scenario. This is a rough implementation to get me started on a more robust application. Maybe even one that has a simple GUI that will detect printers, allow you to select from a drop down list, and then specify the filename.
- - - - - - - - - -
Oh, and it is also digitally signed too!
Not much on command line stuff as I don't do it enough. I can tell you when you type everything in perfectly, it works a mint!
Windows defender complained once I sent the command on its way but I had to convince it I was smarter than it and went for the win.
That should be the last of its rants.
Once the nice message came up I looked and there was the image of my part ready to print.
Great. I don't think I can force the printer to actually start printing. :) So, now that you've seen this, what would you like it to do? And this is now open to others. The link to the tool is:
https://drive.google.com/open?id=1Uq...8Ou7EJ2pHHnNCn
Obvious answer, add it to the editor... I can see an "-andsend" as a modifier to the command lines :)
As code, of course, it is just a vector out of the main program to initiate a print dialog.
If only one printer exits on the network, it default to it. If more than one is found, a list is presented to choose a valid printer.
Extra credit if you can have it determine the printer type and be able to determine what printer is needed for the file presented.
That way the list of printers could only be valid printers. And again, if only one remains, it defaults to it.
Right now, this tool, and the subsequent implementation into the Cube3Editor will only be able to print Cube3 type files. I haven't discovered a way to do cubepro files, unless you have a way for me to get a printer that supports cubepro files really, really, really cheap (basically free)... ;)
So, for Cube3 Files, I could do the following checks:
- Printer model of file against printers found
- Display an error and not allow sending
- Printer material in cartridge against printer cartridges found (i.e., you specified ABS, but printer reports PLA)
- Display an error if material doesn't match (PLA vs ABS)
- Display a warning if color doesn't match, or for that matter, remain silent
- Printer model is cube pro, don't allow enabling of send to printer
- Send to printer is clicked and the file has not been saved (Generate Cube3)
- Display a question dialog that says "File has not been saved, send anyway?"
Now, if I find a way to send a file to a cubepro printer through a similar mechanism, I can update the editor to allow that to happen. But until I have a printer that can accept cubepro files, I am not going to pursue that avenue.
Does the filename extension matter? I can see if it goes to CubePro. I don't know why not. I assumed it would :rolleyes: My bad :p I'll do that tomorrow.
Color shouldn't force a user action.
Abort if material doesn't match w/ message -and- retry option on an indefinite wait-state.
If the command line option works that would be a CubePro out to send a file with a .cubepro extension without validation straight to the IP address. User beware. The printer will process and abort anyway for errors.
Yippi :) did my stuff helped at least a bit ?Quote:
Originally Posted by buddybu
Yes. I have all of the utilities moved to .net core, except the editor. I am in the process of removing the support for the UI library I am using and going with the latest release of the .net core form library. It means that I have to rework the temp, retraction, extrusion input sections. Check again tomorrow, and I will have a branch on my git repository for the .net core version of the utilities.Quote:
Originally Posted by Energyx
awesome! You sticked to VS or did you also take the break to switch to VSC? I try to force myself to call it the preferred Tool for it. It always takes some time to get code from vs to run in vsc even if it is a supported language as .net core ...
so .net core form library? is this "omni channel" ... i think i read about it to be problematic to run outside of a windows host...that's why I was looking into this other thing (forget what it was called)