On Sat, 2012-03-17 at 21:03 +0100, Chr. Rossmanith wrote:
Hi,
some more code removal.
Looks good, pushed this now.
Probably the private variable maTransform can be removed as well: it is
initialized with the identity transform and never changed afterwards.
Does that suggest that the
Hi,
Probably the private variable maTransform can be removed as well: it is
initialized with the identity transform and never changed afterwards.
Does that suggest that the actual call to
mxSprite-transform(maTransform) is actually a no-op ?
At least it doesn't change the position of mxSprite.
On Tue, 2012-03-20 at 15:24 +0100, Chr. Rossmanith wrote:
At least it doesn't change the position of mxSprite. Only the cpu is a
little less idle :-) Then I'll continue to remove maTransform? Or
should it be kept for future use?
I'm not a fan of some day we'll use it, ditch it if it
On Tue, 2012-03-20 at 15:07 +, Caolán McNamara wrote:
I've a shed full of stuff I can't throw out just in case some day we
need it. Not that removing stuff from sdext will give me more space in
my shed I suppose.
:-) I have a similar shed - I can't get into it either ;-) but I