Well, knowing what method you are using will determine what suggestions you get back. If you are using bill boarding, then my suggestions on sphere/cones will be meaningless and completely useless.

Then other thing you can do, is not check when the mouse is down, but when it is back up again. This will give you the advantage that the user may click on the wrong icon and then move the mouse to a "dead area" in an attempt to have nothing happen.

Welcome indeed. And don't be confused by "fb.net", it has nothing to do with Microsofts .NET APIs.

hrm, as I was dealing with other parts of code and making them work, and work with fb .14, I didn't discover this earlier, but pointer lists to pointers seem to be broken. This code generates an error: #Define SDGL_Surface Any Dim Shared Internal_TilePalettes As SDGL_Surface Ptr Ptr Dim TilePtr As S...

It's a target option for the win32 compiler.

Look up the technique called "bill boarding." It is commonly used for this sort of thing. It is also used for explosions, low-quality scenery (bushes, etc), etc.

Modern techniques use textured spheres and/or cones, but you probably want to keep it simple for now.

Ok, two things, let's get the first done now... blah, blah, dead topic, blah, blah resurrecting old threads, blah, blah Second, and the reason: I looked some more into SDL to try to find where it said which version it uses, but now the only reference I can find is to DirectX 5. I could be wrong abou...

Well, a couple things... 1) You are not stating the type of variable that Mouse_X, Mouse_Y and Mouse_B should be. So, since they are not a specific type and you haven't set the default type (Def___ start-finish) they are doubles, iirc. '' WTF are we really??? Dim Mouse_X, Mouse_Y, Mouse_B 2) Since y...

It should be noted that this is apparently only a problem on win32 builds of sdl as it uses DX3 and DX3 doesn't support hardware alpha blending.

On Mac/Linux/FreeBSD/etc, the interfaces it uses *do* support hardware alpha blending and thus you can use hardware surfaces.

hahaha I posted a solution to this several months ago on QBN. Ok, here's your problem: In windowed mode, all surfaces are software surfaces, even the ones allocated as hardware surfaces. This means, everything is in system RAM. In fullscreen mode, surfaces are where you place them, hardware or syste...

Actually, you can do what I do and declare the get/put functions and call them directly. Declare Function fb_FilePut Alias "fb_FilePut" ( ByVal FileNum As Integer, ByVal FileOffset As Integer, ByVal DataPtr As Any Ptr, ByVal Bytes As Integer ) As Integer Declare Function fb_FileGet Alias &...

That's great to hear, but a couple hints to help you get more help in the future: 1) Only post small sections of code which you think the problem is in. Don't post your entire project, no one has time to look at it. 2) Try profiling your code, this is not very hard to do and will show you exactly wh...

The default is implicit, you state you want implicit variable allocation by not stating Option Explicit.

If the programmer is stupid enough to not allocate enough space for the memory to be copied, then the programmer shouldn't be copying memory about. There is no problem with MemCpy Dst, Src, Bytes In fact, it's the standard way of doing it. If you can figure out, "Gee, dst has to be big enough&q...

Not that you should include code modules, but add them properly as separate modules.

FPP is a nice handy-way to do this and maintain code simplicity.

http://ecowles.dyndns.org/bpp/

[/shameless plug]