U were right !!! Sorry for my luck of trust. I had a misteke !
BTW it's not natural - I mean creating a graphics object from image
( offScreen = backimage.createGraphics(); )
then using n changing Graphics object but changes are applied to
image :|
This line suggests that offScreen is created from backimage n this
image is no longer involved
offScreen = backimage.createGraphics();
but than we paint or save backimage :| WHY ?? HOW ??
On Feb 26, 11:54 am, zajekurwabis...@o2.pl wrote:
> U were right !!!
Please note that while some abbreviations
are OK for this group, and others are needed,
abbreviations like 'u', and 'plz' generally
are not liked. Please attempt to spell short
words like 'you' properly. Also, only one '!'
gets the point across!
> Sorry for my luck of trust.
Why should we trust each other? Tests
are always better, and note that I would
not expect someone who does not know me,
to take anyhting I say 'on trust'.
>..I had a misteke !
> BTW it's not natural - I mean creating a graphics object from image
[quoted text clipped - 5 lines]
> image is no longer involved
> offScreen = backimage.createGraphics();
The word 'create' does suggest (to me) that
the Graphic object is 'newly created' and
therefore 'separate' from the BufferedImage,
but it would probably be better called
'getGraphics', ainsce it gets *the* graphics
object of te image, and all changes (lines,
colors, circles) to the graphic, are stored
in the image.
> but than we paint or save backimage :| WHY ?? HOW ??
It shows the Image, as it was after the
last changes made to the graphic object.
(And last note, ALL CAPS is equivalent
to SHOUTING. Please don't shout at me,
because I have a hangover..)
Andrew T.