SDL + BeOS

Hi all sad fellows!

Due to the fact that David O. disagreed with the sdl irc # and there is no
other possibility to get some (really slow) answers. I have to ask some of my
really annoying questions on that really outdated (in comparison to that
really new NNTP protocol) ml right now.

Sorry 'bout that…

Ok, let’s stop kidding right now…

I’ve done some porting to BeOS and experienced a really HIGH latency on key
events.
So, I seems that SDL is eating my CPU power with pleasure when a key keeps
pressed.

Is there anyone out there with BeOS experience, or are there any SDL BeOS
pro’s reachable ?
(Well, any SDL BeOS porter should be able to handle my stupid requests)

Anyone with any experience with BeOS ?

Alex

PS: David please, dont make an endless useless mindless dumpable braindead
thread of that.

PPS: Sam, please kick me of that list if I’m wrong

PPPS: One excuse,… I’m just a braindead guy

Hi all sad fellows!

Due to the fact that David O. disagreed with the sdl irc # and there is no

Well, I didn’t really think it was a bad idea - just that it can’t solve the
problem with the massive OT traffic. Besides, I didn’t think I was such a
major authority around here that I would stop people from setting up an IRRC
channel! :wink:

[…]

I’ve done some porting to BeOS and experienced a really HIGH latency on key
events.

That sounds like what you get with X if you’re not careful… You have to
make sure you’re not buffering up tons of events that would keep the X server
busy, delaying events from the server to your process.

So, I seems that SDL is eating my CPU power with pleasure when a key keeps
pressed.

Do you do anything in response to the events? Do you have an incredibly high
repeat speed? (Like I usually have…)

If you’re trying to do a synchroniced/forced render + flip cycle on every
single event, you’re in for trouble no matter what target you’re on… Mouse
move events are even worse in that respect - unless SDL (or the system)
filter events out when the event queue fills up.

[…]

PS: David please, dont make an endless useless mindless dumpable braindead
thread of that.

Well, I’ll try not to! Besides, I don’t know enough about SDL on BeOS to do
that all by myself. :wink:

//David

.- M A I A -------------------------------------------------.
| Multimedia Application Integration Architecture |
| A Free/Open Source Plugin API for Professional Multimedia |
----------------------> http://www.linuxaudiodev.com/maia -' .- David Olofson -------------------------------------------. | Audio Hacker - Open Source Advocate - Singer - Songwriter |--------------------------------------> david at linuxdj.com -'On Friday 16 March 2001 00:30, Alexander Pipelka wrote:

I’ve done some porting to BeOS and experienced a really HIGH latency on key
events.
So, I seems that SDL is eating my CPU power with pleasure when a key keeps
pressed.

I’ve never seen this before. BeOS doesn’t support my home machine, and I
have to boot in safe mode at work (NVidia GeForce), so I rarely boot into
it. If you can post the minimal example to show this, I’ll take a look at
it when I get a chance.

Is anybody using BeOS anymore? I haven’t heard from anybody at Be lately…

See ya!
-Sam Lantinga, Lead Programmer, Loki Entertainment Software

Hum… I use BeOS =] But I don’t work with SDL yet… [just learning C :P]
Anyway… about the geforce… there are drivers already for it on
www.bebits.com :stuck_out_tongue:

I’ve done some porting to BeOS and experienced a really HIGH latency on
key>> events.

So, I seems that SDL is eating my CPU power with pleasure when a key keeps
pressed.

I’ve never seen this before. BeOS doesn’t support my home machine, and I
have to boot in safe mode at work (NVidia GeForce), so I rarely boot into
it. If you can post the minimal example to show this, I’ll take a look at
it when I get a chance.

Is anybody using BeOS anymore? I haven’t heard from anybody at Be lately…

See ya!
-Sam Lantinga, Lead Programmer, Loki Entertainment Software

Is anybody using BeOS anymore? I haven’t heard from anybody at Be
lately…

Be doesn’t support my machine either (SCSI), as well as it doesn’t support
any of the modern Macs (G4); but I personally like it very much.

Be doesn’t continue to improve it at the time because they are doing their
BeIA, but perhaps in a few years… Then we’ll be the ones with plenty of
BeOS games at hand :slight_smile:

I’ve done some porting to BeOS and experienced a really HIGH latency on
key
events.
So, I seems that SDL is eating my CPU power with pleasure when a key keeps
pressed.

I do have not had any keyboard problems in BeSDL; but that doesn’t mean
anything.

Alexander Pipelka wrote:

I’ve done some porting to BeOS and experienced a really HIGH latency on key
events.
So, I seems that SDL is eating my CPU power with pleasure when a key keeps
pressed.

Isn’t BeOS one of the targets that accepts SDL_INIT_EVENTTHREAD?? Maybe
you should try that flag…

-- David Snopek

/-- libksd –
| The C++ Cross-Platform Game Framework
| Only want to write it once??
| http://libksd.sourceforge.net
------------

Alexander Pipelka wrote:

I’ve done some porting to BeOS and experienced a really HIGH latency on key
events.
So, I seems that SDL is eating my CPU power with pleasure when a key keeps
pressed.

Isn’t BeOS one of the targets that accepts SDL_INIT_EVENTTHREAD?? Maybe
you should try that flag…

It’s actually always enabled, due to the way events are handled in BeOS.

I think there may be a thread starvation issue… ?

See ya,
-Sam Lantinga, Lead Programmer, Loki Entertainment Software

Someone’s helped us by making a BeOS port of Tux Typing. I have used it (and a
few other BeOS ports) quite a bit now, as well as some people on the Tux Typing
mailing list. I, as well as at least one other person, have noticed there can
be some strange latency issues on some BeOS machines that aren’t found on
others.

I felt it was probably due to a lack of hardware support under BeOS. BeOS
doesn’t have quite as many supported devices as Linux does (my primary
platform) or other OSes. So some of the problems we had (graphic, sound
latency) could have easily be due to that.

(Original discussion can be found here:
http://www.geocrawler.com/mail/thread.php3?subject=[Tuxtype-dev]+Re%3A+BeOS+release+of+TuxTyping&list=8561
)On Sat, 17 Mar 2001, you wrote:

I’ve done some porting to BeOS and experienced a really HIGH latency on key
events.
So, I seems that SDL is eating my CPU power with pleasure when a key keeps
pressed.

I’ve never seen this before. BeOS doesn’t support my home machine, and I
have to boot in safe mode at work (NVidia GeForce), so I rarely boot into
it. If you can post the minimal example to show this, I’ll take a look at
it when I get a chance.

Is anybody using BeOS anymore? I haven’t heard from anybody at Be lately…


Sam “Criswell” Hart <@Sam_Hart> AIM, Yahoo!:
Homepage: < http://www.geekcomix.com/snh/ >
PGP Info: < http://www.geekcomix.com/snh/contact/ >
Advogato: < http://advogato.org/person/criswell/ >