On 1 Mar 2010, at 00:12, Riccardo Mottola wrote:
As long of course as core itself doesn't require libobjc-2 feature (which I
hope will be never, but that's tough to say).
I don't have any plans for core to require anything in libobjc2, per se.
There is currently one feature in -base that
Just for the record, I have nothing really to add to either David or
Richard's comments since both of them sum up my feelings on the
subject very succinctly.
We should not sacrifice new features or readability for the sake of
holding on to older architectures and compilers.
Also, the use of
We should not sacrifice new features or readability for the sake of
holding on to older architectures and compilers.
Also, the use of non-c99 standards does hinder contributions since we
constantly expect people who don't have access to c99 based compilers
to change their code to conform to
I just recompiled Gorm and it looks different here :-)
As this is also on a 64bit system the main difference I see is the cairo
version. Could you please try a different backend to confirm that it is
the cairo backend that causes this behaviour.
There are a few places in CarioGState where we
Hi!
I did a test with the art backend, same result. I set a breakpoint in
[ARTContext initializeBackend] to be sure it is actually used. Where is
the code located that is responsible for drawing the NSTabView's
header?
Thanks
TOM
Zitat von Fred Kiefer fredkie...@gmx.de:
I just
[NSTabView drawRect:]
Am 01.03.2010 22:39, schrieb ici...@mail.cg.tuwien.ac.at:
Hi!
I did a test with the art backend, same result. I set a breakpoint in
[ARTContext initializeBackend] to be sure it is actually used. Where is
the code located that is responsible for drawing the NSTabView's
Hi,
just for the record, I'm on Freebsd, x86-ia32, cairo 1.8.8.1 and I
cannot reproduce your problem, cairo works for me.
Riccardo
ici...@mail.cg.tuwien.ac.at wrote:
It's my own application which shows this behaviour. I do not have a
theme enabled, I am using the cairo backend. Everything