On Sat, Feb 9, 2019 at 6:33 PM Michael Van Canneyt
wrote:
> This is not intentional. It can happen we don't see bugs.
Of course this can happen, it happens on the lazarus side as well.
> And I recall distinctly saying several times that you can mail directly if
> you see no-one is reacting.
Yo
On Thu, 7 Feb 2019, Ondrej Pokorny wrote:
Hello,
when working with TFPCanvas, I face an annoying inconsistency between
fcl-image and all other image libraries I know (including LCL Graphics).
The problem is that TFPCustomCanvas.FillRect and all other rect-aware methods
(FillEllipse, etc..
On Sat, 9 Feb 2019, Bart wrote:
On Sat, Feb 9, 2019 at 9:35 AM J. Gareth Moreton
wrote:
I guess I can get a bit impatient,
Reaction time on ptaches in the fpc part of the bugtracker is rather
long (especially when compared to the lazarus part of the bugtracker),
I find that discouraging a
On Sat, Feb 9, 2019 at 9:35 AM J. Gareth Moreton
wrote:
> I guess I can get a bit impatient,
Reaction time on ptaches in the fpc part of the bugtracker is rather
long (especially when compared to the lazarus part of the bugtracker),
I find that discouraging as well.
I have had patches (simple on
fillchar is one useful function, but should be
avoided from use in time critical code by any
cost. Only reasonable way to improve fillchar is
to make it internal function, where fpc can
decide, depending on parameters, what will be best
solution for filling mem with specified value. But
it will
Well, at least we're having a good civil conversation about it! As long
as we can talk and discuss things, then there's no harm, and hopefully
someone like me who is over-enthusiastic at times can still be useful!
I suppose loc[low(loc)] isn't necessarily bad and is guaranteed to be
correct - j
On 09/02/19 08:33, J. Gareth Moreton wrote:
In the last patch that Jonas almost immediately closed, the speed
savings were inconclusive because the number of cycles saved is probably
only a few dozen, but I would argue it makes the code a bit more
reasonable too because it replaces things like
Thanks Michael,
In the last patch that Jonas almost immediately closed, the speed savings
were inconclusive because the number of cycles saved is probably only a few
dozen, but I would argue it makes the code a bit more reasonable too
because it replaces things like loc[low(loc)] with loc[0] and
