computers are real bad. it dithers now and it actually does work (tho looks not so great with the P1) - potential for using more dithering algos in the future due to the AForge.Imaging lib
This commit is contained in:
parent
85ff23a1f9
commit
d9295de186
|
@ -38,10 +38,12 @@ namespace libpaperang.Interfaces {
|
||||||
public short BasePrintDelay {
|
public short BasePrintDelay {
|
||||||
get {
|
get {
|
||||||
switch(PrinterVariant) {
|
switch(PrinterVariant) {
|
||||||
|
//A delay when actually -printing- is necessary; moreso with the P2 model, as higher DPI means more packets for the same physical length of paper
|
||||||
|
// and when faced with a print data buffer exhaustion, the printer will simply discard what's in the buffer and start printing whatever data is received after
|
||||||
case BaseTypes.Model.P1:
|
case BaseTypes.Model.P1:
|
||||||
return 80;
|
return 100;
|
||||||
case BaseTypes.Model.P2:
|
case BaseTypes.Model.P2:
|
||||||
return 140;
|
return 170;
|
||||||
default:
|
default:
|
||||||
throw new InvalidOperationException();
|
throw new InvalidOperationException();
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue