In the print() method look at the graphics transform and scale down
accordingly.
Eg if the printer is 360 dpi, then the transform will report a scale of
(5,5) so you need
to apply a user scale of 1/5, 1/5.
Then a 1 pixel user space line will be 1 device pixel.
FYI printers that say they are
Hello,
[EMAIL PROTECTED] wrote:
Try one of my applets and go fullscreen:
http://pancyl.com/
Press F1 to enter -- ESC to exit.
When you enter, the border flashes blue and there is a little icon on the upper
right that gives a floating announcement that this is a Java window. This is
much,
Try one of my applets and go fullscreen:
http://pancyl.com/
Press F1 to enter -- ESC to exit.
When you enter, the border flashes blue and there is a little icon on the upper
right that gives a floating announcement that this is a Java window. This is
much, much better than the banner at the b
Since I have not received an answer to my previous question, I will try to
simplify it even further.
For an arbitrary printer, how can I print a single line that is one printer
"dot" wide by N dots long, ie, print the finest line the printer is capable of
printing?
For a 300dpi printer this l
[EMAIL PROTECTED] wrote:
Thanks for the tip. I have added methods to check property changes to the size and text.
I also read somewhere that I should not override the paintComponent method but that I should use the paint method instead. The clip is normally set in the paint method of JComponent.
The tags you're looking for are [ code ] and [ /code ] but remove the spaces
in the tags! Put that around your code and the forum software will pretty print
it for you.
Also, wherever you read which method to override for JComponent is wrong. You
should be overriding paintComponent() in virtua
Thanks for the tip. I have added methods to check property changes to the size
and text.
I also read somewhere that I should not override the paintComponent method but
that I should use the paint method instead. The clip is normally set in the
paint method of JComponent.
If I do that it also wo
Thanks for the report.
This problem is most likely caused by this bug:
http://bugs.sun.com/view_bug.do?bug_id=6635462
The OUTLINE drag mode in internal frames uses XOR, which causes this bad
performance you see. Just don't use OUTLINE drag mode in your application.
Thanks,
Dmitri
[Message s