Talk:Colour pinstripe/Printer: Difference between revisions
Sure
No edit summary |
(Sure) |
||
| (One intermediate revision by one other user not shown) | |||
Line 8:
Yes, after an inch the pinstripe is 2 pixels wide, after a foot, it's 12 pixels wide, after 10 feet, it's 120 pixels wide. But I am not quite sure what this means for an HP Designjet with a full roll of paper. --[[User:Rdm|Rdm]] 15:20, 23 May 2011 (UTC)
: Perhaps a reasonable limitation would be "no fewer than three color cycles, and then no greater than one square"? (where square would be the largest equal-logical-width, equal-logical-height space--a 1ftx250ft roll would produce a 1ft square.) Go three cycles, and then continue up to 1-square. Also...I wonder what Windows' GetDeviceCaps reports for that printer for HORZSIZE, VERTSIZE, HORZRES and VERTRES --[[User:Short Circuit|Michael Mol]] 15:55, 23 May 2011 (UTC)
:: If you have some simple code I can build under VS2010, I could run it and show you the output. But the [http://support.microsoft.com/kb/193943 example code I saw for GetDeviceCaps] was too much of a side track for me. --[[User:Rdm|Rdm]] 17:57, 23 May 2011 (UTC)
::: Sure. Using VS2010 here at work. Don't know exactly how soon I'll be able to write it, but I'll look into it. --[[User:Short Circuit|Michael Mol]] 18:19, 23 May 2011 (UTC)
The task is really to demonstrate the coding. You could always adjust the run length and step distances for a specific implementation in live code (Maybe set variables at the top of the code). I don't think we need to worry about that for the purpose of this task. As long as the
task demonstrates the fine control of the printer, a reader would be able to wield the techniques demonstrated to achieve their specific goals.
I think the term square is more confusing, because a square could be any size, whereas a pixel means the smallest dot (possibly a tridot) that the printer can produce.
[[User:Markhobley|Markhobley]] 15:57, 23 May 2011 (UTC)
| |||