BYO games plugin :)

[MortenMacFly]

Here is what I did. [...]

I can confirm this. It happened to me, too. But I believe byo knows best where to look for it... ;-)

[access violation] I was using this nightly.

What shall we do with this report? Come on, you could have at least provided the crash report...

With regards, Morten.

[sethjackson]

[access violation] I was using this nightly.

What shall we do with this report? Come on, you could have at least provided the crash report...

With regards, Morten.

Umm well that is the thing. No *.rpt was generated......  :?

[MortenMacFly]

Umm well that is the thing. No *.rpt was generated......  :?

Ok... that explains pretty well why you did not... :lol: :lol: :lol:

[sethjackson]

Umm well that is the thing. No *.rpt was generated......  :?

Ok... that explains pretty well why you did not... :lol: :lol: :lol:

:lol:

[byo]

Umm there is a not so nice problem with this plugin.......

Here is what I did.

1. Plugins -> BYO Games -> C::B-Tris -> Play.
2. Right click on the C::B Tris tab -> Close.
3. I started coding.
4. After 10min I get this message box telling me to get back to work. I hit Ok. (I'm not even running the game). I get this message box over, and over (yea I could check don't annoy me but I don't). Close C::B.
5. Re-start C::B.
6. Access violation......

Anyways the message box is the bug. I wasn't even playing the game, and it told me to get back to work.  :lol:

I guess the access violation could be a bug too.

I was using this nightly.

http://forums.next.codeblocks.org/index.php?topic=3378.0

With wx 2.6.3.

Yop, that was one small thing I've forgotten to add into destructor  :oops:. The only thing I don't really understand is access violation after restarting C::B. All games state is currently reset when restarting (nothing read from configuration). So it should work fine. Maybe it's caused by multiple instances of AnnoyingDialog  :?

[Michael]

Hello,

I have tried the game on my fresh compiled C::B (.deb package rev2586, Ubuntu Dapper) and now the arrow keys seem to work . Anyway, the game is very slow and the mouse cursor is blinking all the time when it is inside the game's window :?.

Best wishes,
Michael

[byo]

Hello,

I have tried the game on my fresh compiled C::B (.deb package rev2586, Ubuntu Dapper) and now the arrow keys seem to work . Anyway, the game is very slow and the mouse cursor is blinking all the time when it is inside the game's window :?.

Best wishes,
Michael

Thx for info.
Whats your CPU ? And what do you mean by saying "slowly" ? Does it work slowly or respond for keyboard with delay ? I've tested on gentoo and it worked almost fine for me.

[Michael]

Thx for info.
Whats your CPU ? And what do you mean by saying "slowly" ? Does it work slowly or respond for keyboard with delay ? I've tested on gentoo and it worked almost fine for me.

Hello,

I have a PIII 500MHz and around 500MB RAM.

The games works slowly and responds slowly (with delay).

Best wishes,
Michael

[sethjackson]

Umm there is a not so nice problem with this plugin.......

Here is what I did.

1. Plugins -> BYO Games -> C::B-Tris -> Play.
2. Right click on the C::B Tris tab -> Close.
3. I started coding.
4. After 10min I get this message box telling me to get back to work. I hit Ok. (I'm not even running the game). I get this message box over, and over (yea I could check don't annoy me but I don't). Close C::B.
5. Re-start C::B.
6. Access violation......

Anyways the message box is the bug. I wasn't even playing the game, and it told me to get back to work.  :lol:

I guess the access violation could be a bug too.

I was using this nightly.

http://forums.next.codeblocks.org/index.php?topic=3378.0

With wx 2.6.3.

Yop, that was one small thing I've forgotten to add into destructor  :oops:. The only thing I don't really understand is access violation after restarting C::B. All games state is currently reset when restarting (nothing read from configuration). So it should work fine. Maybe it's caused by multiple instances of AnnoyingDialog  :?

Yea I couldn't reproduce the access violation. Maybe it was the way I closed C::B. I dunno.  :?

[tiwag]

for those who want build ByoGames plugin on Linux using a CB project (like me)

here is a working byogames-unix project file attached.

[edit] file removed here and comitted to svn

[tiwag]

Thx for info.
Whats your CPU ? And what do you mean by saying "slowly" ? Does it work slowly or respond for keyboard with delay ? I've tested on gentoo and it worked almost fine for me.

Hello,

I have a PIII 500MHz and around 500MB RAM.

The games works slowly and responds slowly (with delay).

Best wishes,
Michael

CBtris works on my AMD XP 2800 with 1024MB ram
on Ubuntu 5.10 and is also really "slow" compared to the Windows version
running on the same computer.

[Michael]

Thx for info.
Whats your CPU ? And what do you mean by saying "slowly" ? Does it work slowly or respond for keyboard with delay ? I've tested on gentoo and it worked almost fine for me.

Hello,

I have a PIII 500MHz and around 500MB RAM.

The games works slowly and responds slowly (with delay).

Best wishes,
Michael

CBtris works on my AMD XP 2800 with 1024MB ram
on Ubuntu 5.10 and is also really "slow" compared to the Windows version
running on the same computer.

Hello,

I have just tried C::B rev 2592 on the same machine, but with Gentoo and it seems that now the game works fine. It is no more slow and perfectly playable . Anyway, I will give a try on Ubuntu Dapper too.

Best wishes,
Michael

[Denis]

I played several minutes amd close the game. After some time I saw message "Stop playing and begin to work" (or something like this) I closed message but it popuped again. Only closing C::B helped with this problem

[tiwag]

this reminder-shit should be removed clompletely from the code

[byo]

I played several minutes amd close the game. After some time I saw message "Stop playing and begin to work" (or something like this) I closed message but it popuped again. Only closing C::B helped with this problem

It has already been fixed.

this reminder-shit should be removed clompletely from the code

No, it won't be removed. But it will be configurable in future.