I'm running straight out of SVN so have the most recent features and
bugs:) This is on a 10.4 Intel box with an ATI Radeon X1600.
Everything is compiled and run with --with-flavour OSX (that is my
only option at this point).
wrt Full Screen Mode: perhaps I didn't explain properly, but the
vanilla C version of the program enters full-screen mode just fine.
However, the OCAML version (which as I said, I'm 99% sure executes
exactly the same sequence of calls into the clutter API) does not
enter full-screen mode. i.e. I set the property, check it, and it is
still set to false. So, it just seemed very odd that the C version
worked and the OCAML one didn't and I didn't have a logical
explanation. It made me think that there is some underlying decision
making process wrt full-screen mode that is affected by how the
program is compiled, executed, started etc. Since I have a working C
version and broken OCAML version, I can certainly at some point
narrow it down to exactly what the difference is that causes this,
however, it may be somewhat painstaking. I was just posting this on
the off-chance that somebody had a one line explanation.
wrt The Test Program: I will file bugs on ones which aren't working.
I feel compelled to perform a minimum amount of debugging on my own
before filing bugs on these, but I'll try to get them into the system
initially and then hopefully find some time to perform some
debugging. There are a couple test programs that I'm not sure what
the intended behaviour/success criteria. I very short README file
would do wonders (I know, I know, that makes me a volunteer)
- Reid
On 3-Jul-08, at 10:00 AM, Emmanuele Bassi wrote:
On Thu, 2008-07-03 at 14:52 +0100, Matthew Allum wrote:
Hi;
On Thu, 2008-07-03 at 08:54 -0400, Reid van Melle wrote:
Sorry for this dump of questions...
1. Full Screen Mode
What version of Clutter are you using here and with what backend ?
I think fullscreen on OSX (the one that Reid is using, as far as I
understood) is not entirely working:
http://bugzilla.openedhand.com/show_bug.cgi?id=545
3. Clutter Test Programs
There are a few test programs (i.e. cluttter/tests/*) that crash and
potentially a few others that are not executing properly. Is this
expected? Or is every instance of a failing test program a bug that
should be investigated and filed?
Again what version and backend are you using here ? Either way these
'tests' shouldn't crash - if they do please do post a bug on
bugzilla.
yes, some tests do crash on OSX; I've been going over them on the 10.5
with i965 box we have, but could not figure out why. most of the
crashing ones were the COGL tests, as far as I could see.
an open bug about them would be great indeed.
ciao,
Emmanuele.
--
Emmanuele Bassi, OpenedHand Ltd.
Unit R, Homesdale Business Centre
216-218 Homesdale Rd., Bromley - BR12QZ
http://www.o-hand.com
--
To unsubscribe send a mail to [EMAIL PROTECTED]
--
To unsubscribe send a mail to [EMAIL PROTECTED]
