search

Ultimaker / Cura

3D printer / slicing GUI built on top of the Uranium framework
GNU Lesser General Public License v3.0
6.22k stars 2.08k forks source link

CLI mode: stdout and stderr not visible #5780

Open thopiekar opened 5 years ago

thopiekar commented 5 years ago

Application Version 4.0.0

Platform Windows

Printer Doesn't matter

Steps to Reproduce Running "CuraCLI.exe --help" in PowerShell

Actual Results No output

Expected results Output as I implemented it about one year before (Cura 3.2): Inkedsnip_20171209231218_LI The beginning was noisy as it gave debug info from the initialization, but I was able to see the parser's output at the end. The plugin I'm working on needs to add command line options and I want to see the output directly instead of wasting time in looking for the stdout and stderr file.

Additional Information Please bring this functionality back. The stdout and stderr files are not useful during development as getting direct feedback from Cura via command line. I have the suspect that this functionality has been removed during a cleanup months before.

thopiekar commented 5 years ago

Additionally, I noticed that I can't register command line options within my plugin anymore. Have the feeling that https://github.com/Ultimaker/Uranium/pull/491 will fix it, but haven't tested it.

Again, please bring this functionality back. I need this to continue on my project.

usage: cura [--version] [--external-backend] [--headless] [--debug]
            [-qmljsdebugger QMLJSDEBUGGER] [--help] [--single-instance]
            [--trigger-early-crash]
            [file [file ...]]
cura: error: unrecognized arguments: --register_com
thopiekar commented 5 years ago

@Ghostkeeper Can you give me an update on whether this problem is somewhere on your board? Or not?

Thanks 😉 👍

Ghostkeeper commented 5 years ago

Yeah we discussed it this morning and added it (CURA-6549).

thopiekar commented 5 years ago

Is there any statement you can give regarding priority? Do you need the current state of the plugin which makes use of this functionality, so you have something to test? If there is anything I can do, please let me know!

Ghostkeeper commented 5 years ago

As discussed this morning, we didn't set a priority on this yet. If nothing is done, the priority will be low. I'll leave it up to @diegopradogesto and his stakeholders to decide on the priority.

That pull request probably gets done much quicker since it is less work for us. So hopefully that'd fix this too.

GregValiant commented 1 week ago

I'm cleaning house. Is this still a problem with current Cura versions (5.8.0 and up)? Can I close this?