1006
General discussions / SFML 1.3 and OS X
« on: July 22, 2008, 02:09:25 am »
Till now, I didn't find anybody.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
1007
General discussions / SFML 1.3 and OS X
« on: July 15, 2008, 01:47:59 pm »
Hum... some bad news now : there are still troubles (that make app crash), but once again, I can't get it to crash on my own computer. So... I'm going to look for someone that knows Cocoa, OpenGL, C++ and Obj-C and that is using an Intel Mac in order to find the mistake.
I can't drop code myself to find it because it never crashes. I dunno if someone here would be able to do this, anyway I'm also going to look for helpers on some other forums.
I can't drop code myself to find it because it never crashes. I dunno if someone here would be able to do this, anyway I'm also going to look for helpers on some other forums.
1008
General discussions / SFML 1.3 and OS X
« on: June 29, 2008, 09:51:13 pm »
Thanks for your feedback and your encouragement 
.
Some news...
- Added one missing code for sf::Key::Return
- Added File menu
- Updated shorcuts handling (using one is now visible in the menu bar)
That's all for now
.
.Some news...
- Added one missing code for sf::Key::Return
- Added File menu
- Updated shorcuts handling (using one is now visible in the menu bar)
That's all for now
.
1009
General discussions / SFML 1.3 and OS X
« on: June 27, 2008, 02:10:09 pm »
Some news...
- Testers told me it does no more crash.
- Added "Window" menu.
- Fixed trouble with the "About" panel (couldn't close it).
- Added individual window event handling (I was using every Cocoa events for the first window :- °).
- Fixed mistake with mouse coordinate (there was a gap on the Y axis).
- Added Command, Control, Option and Shift key handling. That means event handling is finished except a problem with languages handling. I made the main keys independant from keyboard layout but there are still some that aren't. There is no trouble with TextEntered events (only with KeyPressed and KeyReleased).
That's all for now .
- Testers told me it does no more crash.
- Added "Window" menu.
- Fixed trouble with the "About" panel (couldn't close it).
- Added individual window event handling (I was using every Cocoa events for the first window :- °).
- Fixed mistake with mouse coordinate (there was a gap on the Y axis).
- Added Command, Control, Option and Shift key handling. That means event handling is finished except a problem with languages handling. I made the main keys independant from keyboard layout but there are still some that aren't. There is no trouble with TextEntered events (only with KeyPressed and KeyReleased).
That's all for now
.
1010
General discussions / SFML 1.3 and OS X
« on: June 25, 2008, 12:30:30 am »
Okay, anyway don't worry. You have time as I still have much work to do in order to finish the port.
Still to do for now :
- event handling (almost done)
- handle fullscreen mode (not started yet)
- handle joysticks (not started yet)
- correct every bugs (huuh... we'll see )
Still to do for now :
- event handling (almost done)
- handle fullscreen mode (not started yet)
- handle joysticks (not started yet)
- correct every bugs (huuh... we'll see
)
1011
General discussions / SFML 1.3 and OS X
« on: June 24, 2008, 11:22:45 pm »
Thanks .
Were you able to run the test program ?
.Were you able to run the test program ?
1012
General discussions / SFML 1.3 and OS X
« on: June 24, 2008, 09:59:07 pm »
I've some news for you.
I've done much tries, dropping most of my work and yet I've still noticed troubles (data corruption).
This morning I thought of something that was actually... quite true. That means I finally found why everything was going wrong.
If you have looked at my work, you may have noticed a #ifdefined(__OBJC__) block inside of the WindowImplCocoa class declaration. This was allowing me to use objc-C objects among the other members of the C++ class. C++ files couldn't see these members and anyway, they wouldn't have liked to. So everything looked fine.
But ! ...as these members weren't visible from the C++ files, when allocating memory for a WindowImplCocoa object, memory was allocated only for the visible members. That means I was using members located in a non-allocated memory zone, and the following allocations were changing the value of my members.
Well... now I would enjoy being positive. I fixed that and... I would like you to tell me if everything works fine .
Note: I didn't say the port was completely done.
PS: I hope my frenchy English is somewhat fine .
I've done much tries, dropping most of my work and yet I've still noticed troubles (data corruption).
This morning I thought of something that was actually... quite true. That means I finally found why everything was going wrong.
If you have looked at my work, you may have noticed a #ifdefined(__OBJC__) block inside of the WindowImplCocoa class declaration. This was allowing me to use objc-C objects among the other members of the C++ class. C++ files couldn't see these members and anyway, they wouldn't have liked to. So everything looked fine.
But ! ...as these members weren't visible from the C++ files, when allocating memory for a WindowImplCocoa object, memory was allocated only for the visible members. That means I was using members located in a non-allocated memory zone, and the following allocations were changing the value of my members.
Well... now I would enjoy being positive. I fixed that and... I would like you to tell me if everything works fine
.Note: I didn't say the port was completely done.
PS: I hope my frenchy English is somewhat fine
.
1013
General discussions / SFML 1.3 and OS X
« on: June 23, 2008, 05:41:30 pm »
Uh... nop. Testing my work is quite simple as all dependencies are already installed. You just need to get the stuff from the SVN repository (using "svn co http://sfml.svn.sourceforge.net/svnroot/sfml" in Terminal.app), open the project sfml/build/xcode/SFML.xcode, select the 'sfml-testing' target, and click the 'Build and Run' button.
You don't have to take care of the packages required by the test program, everything is done automatically.
What's trickier is compiling the audio and graphic package because of the dependencies, but that's not the purpose here.
You don't have to take care of the packages required by the test program, everything is done automatically.
What's trickier is compiling the audio and graphic package because of the dependencies, but that's not the purpose here.
1014
General discussions / SFML 1.3 and OS X
« on: June 23, 2008, 11:29:10 am »
Thanks. I'll tell you as soon as I've news .
.
1015
General discussions / SFML 1.3 and OS X
« on: June 23, 2008, 11:17:17 am »
I'm making the port. The point is just I can't get my work to crash (I use Mac OS X 10.3) whereas it does on Mac OS X 10.4 and 10.5. I expect to get a new laptop with Mac OS X 10.5 in about 2 weeks (if I pass my exams). So... let's hope everything will be fine for me (I mean for my exams) and I'll fix what's wrong .
Note : the port will be up to date. There are just still a few points... joysticks should come later and the Audio package does not work because of OpenAL (which isn't updated anymore).
.Note : the port will be up to date. There are just still a few points... joysticks should come later and the Audio package does not work because of OpenAL (which isn't updated anymore).
1016
General discussions / Current Mac OS X status
« on: June 09, 2008, 08:49:31 pm »
It depends on the Mac OS X version you're using. I wasn't able to make my work crash on my Mac 
(10.3), but it does crash with 10.4 and 10.5.
You can have a look at the sources from the SVN repository and tell me if you notice something relevant. Otherwise you can wait for me to finish the port. It should be ready in less than a month (time to take exams and get my laptop).
The point isn't really a lack of time but my "old" Mac OS X version.
(10.3), but it does crash with 10.4 and 10.5.You can have a look at the sources from the SVN repository and tell me if you notice something relevant. Otherwise you can wait for me to finish the port. It should be ready in less than a month (time to take exams and get my laptop).
The point isn't really a lack of time but my "old" Mac OS X version.
1017
General discussions / Hi, I'm user n.500 ^_^ What I win?
« on: May 12, 2008, 07:08:30 pm »Quote from: "quasius"
It's also cross-platform as you requested.
It's supposed to be so, but it's not. They are currently looking for someone to make it work on Mac OS X.
I couldn't get it to compile.
1018
General discussions / Current Mac OS X status
« on: April 26, 2008, 06:29:49 pm »Quote from: "Laurent"
This is the official port. I think Ceylo was talking about this summer, not the next year's one
I indeed meant "this" summer :mrgreen: . I thought "this" and "next" meant the same here...
1019
General discussions / Current Mac OS X status
« on: April 26, 2008, 05:29:11 pm »
Uh... I'd say it'll be ready for next summer (yeah I know it's wide and a long way :roll: ) but I can't be positive. It depends on whether I quickly fix the remaining bugs.
I expect the port to be ready only for next summer because as a 17 years old boy I'm a bit busy, I've got homework, exams in about 2 months... but the good point is I'll probably get a new laptop (in june or july) and I'll able to do much more tests for miscellaneous Mac OS X versions. I'm currently using Mac OS X 10.3.
P.S.: I'm French and trying to improve my English. Please tell me my mistakes if you notice some.
I expect the port to be ready only for next summer because as a 17 years old boy I'm a bit busy, I've got homework, exams in about 2 months... but the good point is I'll probably get a new laptop (in june or july) and I'll able to do much more tests for miscellaneous Mac OS X versions. I'm currently using Mac OS X 10.3.
P.S.: I'm French and trying to improve my English. Please tell me my mistakes if you notice some.
1020
Feature requests / How to port the Linux source of SFML 1.2 to Mac OS X?
« on: April 25, 2008, 08:36:16 pm »
A few weeks uh.... it depends on whether I can quickly fix the remaining problems (still crashing for now).
I would rather say it'll be ready for next summer as I'll get a new laptop and I'll be able to test my work quite easily. I'm currently using Mac OS X 10.3...
It MIGHT be ready earlier, but I can't be positive.
I would rather say it'll be ready for next summer as I'll get a new laptop and I'll be able to test my work quite easily. I'm currently using Mac OS X 10.3...
It MIGHT be ready earlier, but I can't be positive.