Writing a better 2D engine. (Phoenix 2D Game Engine)

**Traveler** · 20-03-2007, 11:14 PM

A bit off topic, but your game looks very professional. You really should create annother thread about it, with some additional info on how you made it, how long it took, a screenshot, etc. I or one of the another admins will most likely make an newsitem out of it.

As for your Phoenix changes suggestion, I can only agree with that.

**Andreaz** · 21-03-2007, 06:17 AM

Originally Posted by wagenheimer

I¬¥have implemmented a lot of new things to Phoenix... but my code is a mess! I did see that there more people here implemmenting news things to the engine.... it would be nice to everybody that changed things, comment it and show here what was doing. What did you think?

Great idea!

The source and demo for the canvas stuff is avaiable here:

http://www.phoenixlib.net/files/Canvas.zip

Don't feel that the whole lib is in a state for release atm, need to test so nothing has broke

**Andreaz** · 23-03-2007, 06:24 AM

Originally Posted by Galfar

I just don't want that 1MB FreeImage DLL so I will add alternative loader.

Oh, i see. Have you taken a look at the texture loading framework in phxTexture, as you see it's plug and play and it's really easy adding a different loader then freeimage. If you need any help with this, please let me know

**Galfar** · 25-03-2007, 12:10 AM

Originally Posted by Andreaz

Oh, i see. Have you taken a look at the texture loading framework in phxTexture, as you see it's plug and play and it's really easy adding a different loader then freeimage. If you need any help with this, please let me know

Yes, it looks quite easy. I'll let you know if will have some questions.

Just one unrelated question: do you know a way of telling Phoenix's glfw window not to have a maximize button and not to allow resizing?

**Andreaz** · 25-03-2007, 03:58 PM

Originally Posted by Galfar

Just one unrelated question: do you know a way of telling Phoenix's glfw window not to have a maximize button and not to allow resizing?

Well, there's some code that in the CVS repository of glfw for it, but it hasn't been relased or compiled to a dll yet, but i suppose it's in the pipe.

**godbeast** · 12-04-2007, 05:28 PM

I came up with something like this (fpc messages):

First compilation of e:\projekty\fpc\2.0.4\units\phoenix\src\phxscreen. pas
phxscreen.pas(474,47) Error: Incompatible type for arg no. 1: Got "<address>", expected "<procedure>"
phxscreen.pas(475,46) Error: Incompatible type for arg no. 1: Got "<address>", expected "<procedure>"
phxscreen.pas(547,42) Error: range check error while evaluating constants
phxscreen.pas(60

Fatal: There were 3 errors compiling module, stopping
phxscreen.pas(60

Fatal: Compilation aborted

What's wrong? I don't mess with fpc cfg, I use standard configuration and my version is 2.0.4. I'll fight by myself right now, but if somebody knows the solution?

**godbeast** · 12-04-2007, 05:30 PM

And this is when it happens:

In phxscreen.pas: glfwSetWindowCloseCallback(@WindowCloseEvent);
Line 474

**Andreaz** · 14-04-2007, 06:31 AM

Hmm, that's strange i have 2.0.4 aswell but i don't get that error, anyone has any ideas of what's causing it ?

**godbeast** · 14-04-2007, 09:05 AM

These comes out when I try to compile with standard fpc configuration mady by installer. When I change certain options, fpc shows other strange errors.

If you have 2.0.4 also, I think that reasons could be either my config file for fpc or I messed up with Phoenix installation. I just added phoenix\src and phoenix\lib directories to fpc units path. Should I do something more?

**Galfar** · 15-04-2007, 01:07 PM

Originally Posted by Andreaz

Oh, i see. Have you taken a look at the texture loading framework in phxTexture, as you see it's plug and play and it's really easy adding a different loader then freeimage. If you need any help with this, please let me know

I've added texture loader which uses Vampyre Imaging Library to load/save image instead of FreeImage. As you wrote, it was really easy to extend Phoenix in this way. If you are interested the modified source is here: http://galfar.vevb.net/temp/phx/phxTexture.pas.

But I have a question about GUI. In archive labeled "Demo of the editors (particle, image, animation and gui)" on phoenixlib.net is GUI editor with listbox and scrollbar controls and whole GUI uses controls.phximg for skinning. However, archive with source code contains some different version of GUI engine (without listbox and without using patterns for skinning). Which one of those should be used? Any chance you could upload current GUI engine somewhere?