Show all posts by user
Page 1 of 1 Pages: 1
Results 1 — 3 of 3
Of course. Or any other non-infered output. (Per your suggestion, I did also do a simple STDOUT redirect in Slic3r, but evolved to the method shown below as it's more explicit)
Which works. It did turn up some odd path naming
use strict;
use warnings;
print "A printed text line";
open OUTPUT, ">d:/output.txt";
print OUTPUT "This is some output\n";
close OUTPUT;
Only "This is some output
by
laserted
-
Slic3r
J-
the notepad weirdness has come and gone, per above; it seems to have been a CitrusUtils glitch. Doubleclicking the script at any time in the experience always did run the script in a perl terminal; of course since the script was expecting a file to be passed to it, it would hang in that method, but that is normal behaviour.
For giggles, I tried a clean "hello world test with keypress" test;
by
laserted
-
Slic3r
Greets -
I've been attempting to get Slic3r post scripts running in a Win64 environment, but no luck.
I do have a working (standalone) Slic3r 0.9.10b running fine, with CitrusPerl installed as well as the dependencies to build Slic3r from scratch. I am not running Slic3r from source, just the precompiled package.
I've been testing with the post scripts included in the Slic3r package, and am con
by
laserted
-
Slic3r