2009/9/30 Alan Grimes
> =P
>
> When I get on a ktechlab roll, I just can't stop myself. =(
>
> I wish I was like this with my income generating work. =(((
>
> This time I've really done it.
>
> Say goodbye to another few dozen lines of supremely dodgy code in
> Simulator! =)
>
> As an added b
Soryy... my mistake... is the 455 revision looks that the bug dissapear...:)
Now ktl don't crashes when deleting components or closing some circuit
documents.
2009/9/30 santiago gonzalez
>
> I don't know exactly what bug are you talking about, i tried revision 450
> (undo commit 447) and now 45
santiago gonzalez wrote:
> I'm compiling your last commit and have this error:
> _
> ecclockinput.cpp: In constructor
> 'ECClockInput::ECClockInput(ICNDocument*, bool, const char*)':
> ecclockinput.cpp:54: error: '
I don't know exactly what bug are you talking about, i tried revision 450
(undo commit 447) and now 455 and ktl crashes when deleting some components
or closing some circuit documents.
If this can help, Kcrash always say this:
_
[T
I'm compiling your last commit and have this error:
_
ecclockinput.cpp: In constructor 'ECClockInput::ECClockInput(ICNDocument*,
bool, const char*)':
ecclockinput.cpp:54: error: 'stepCallback' is not a member of 'E
=P
When I get on a ktechlab roll, I just can't stop myself. =(
I wish I was like this with my income generating work. =(((
This time I've really done it.
Say goodbye to another few dozen lines of supremely dodgy code in
Simulator! =)
As an added bonus, try out a circuit with an one of thos
Thanks to you, I wasted my day on ktechlab instead of earning
desperately needed money. Gee thanks, Zoltan...
I just committed a fairly radical patch which replaces our old set of
really nasty bugs with regards to displaying wire currents with a
completely new set of simpler bugs. The new code is
On Tue, 29 Sep 2009 22:11:55 +0200, Alan Grimes
wrote:
> P Zoltan wrote:
>> Let's start this mail with a famous quote:
>>
>> "There are two ways to write code: write code so simple there are
>> obviously no bugs in it, or write code so complex that there are no
>> obvious bugs in it."
>>
>>
P Zoltan wrote:
> Let's start this mail with a famous quote:
>
> "There are two ways to write code: write code so simple there are
> obviously no bugs in it, or write code so complex that there are no
> obvious bugs in it."
>
> It seems that if I revert the commit that has removed the usa
Let's start this mail with a famous quote:
"There are two ways to write code: write code so simple there are
obviously no bugs in it, or write code so complex that there are no
obvious bugs in it."
It seems that if I revert the commit that has removed the usage
QGuardedPtr class in som
On Tue, 29 Sep 2009 20:56:02 +0200, Alan Grimes
wrote:
> I followed my own advice and loaded the latest fixmes... Here's an
> interesting one in a function in code that I designed, wrote, and
> contributed.
>
> Zoltan thinks I have a bug here so let's see if we can explicate the
> code
>
>
11 matches
Mail list logo
