ENIGMA Development Environment

Ohhh ok I see, probably a conflict between the two since DirectShow actually utilizes Direct3D, also, DirectX is the incorporation of all those Direct* API's, people make the mistake of calling Direct3D DirectX when it is really just a part of it, I used to do the same until I realized how many different parts of DirectX there actually are. But anyway, we may need a ffmpeg or some other sort of extension to make the OpenGL ones as I said, because I look to having the feature Unity3D does where they can be loaded and rendered directly to a surface and shown as a billboard in-game.

https://github.com/enigma-dev/enigma-dev/pull/485

TKG, I added CD functions for you, I'm just waiting for someone to merge. Btw, your graphics skills are awesome 

lol, funny as shit

I found the documentation on them.
http://msdn.microsoft.com/en-us/library/windows/desktop/ms646299%28v=vs.85%29.aspx

Well, someone find me a download because the links broken

For me it was Game Maker 6.0 I started with.

http://bentibbetts.net/animo/

Just for fun I am going to download some and run them in an emulator.

It is also really funny to notice that Game Maker has not changed much at all since Game Maker 5. It is also kind of funny how 1.4 to 5 all run on Windows 7 except GM6.1

Well I didn't say nothing used registry. But the less a program uses it the better.

Well I am sorry Harri, but you are simply wrong this was the entire purpose of the registry.
http://en.wikipedia.org/wiki/Windows_Registry
" With the introduction of Windows 95 and Windows NT, its use was extended to tidy up the profusion of per-program INI files that had previously been used to store configuration settings for Windows programs."

They could make a 5k$ product that can only do show_message() and you shouldn't care.

Unity3D's free version can do all that they do and more and do it better, because they have the power of a full programming language.

The quote you made was me talking about hardware functions.

Again, the Windows registry is not a hardware feature, and neither are disk and storage functions for audio and media playback, what if somebody wanted to create a really really cool media player that was half media player and half video game or something? With Unity3D you have that power, with BlitzBasic you have that power and cross-platform. Another thing I just added that they had removed was video playback support using DirectShow, later I intend to add the functions so video's can be rendered to Direct3D surfaces using the COM interface.

They consider it a tool for making a specific type of software - games.

Again, that is what Unity3D and BlitzBasic are meant for, yet people use them to create all kinds of other applications. Same with Qt being mainly a cross-platform GUI framework, and people use it to make games.

Is that the physics part accelerated?

No, Box2D is not hardware accelerated which makes it nice for mobile and shit. Which is also why I've written a Bullet extension which can be used for hardware accelerated 2D and 3D physics. I may do one more collision system which doesn't handle physics but does 2D and 3D collision detection as an alternative to BBox and Precise since cheeseboy and others have been requesting it.

That thing basically didn't even support internet.

As I said before I have no intention of even bothering to make that DirectPlay networking system work, the code is a clusterfuck and it was a very very poor API by Microsoft.
http://en.wikipedia.org/wiki/DirectPlay

and ini functions require an extension to be used on non-windows platform.

http://en.wikipedia.org/wiki/INI_file
"Linux and Unix systems also use a similar file format for system configuration. In addition, platform-agnostic software may use this file format for configuration. It is human-readable and simple to parse, so it is a usable format for configuration files that do not require much greater complexity."
You are almost as bad as Josh, can we please stop all the hate on INI files? YAML is 1000x more shittier and does not leave room for mistakes either, eg. indentation.

And again, nobody should ever use that function. That is only used for debugging.

Texturing a message dialog to make it look pretty, is for debugging?

And the reason for removal of course is that this also cannot be easily ported.

*ahem* They can be ported, you can texture XLIB dialog and Mac dialogs, if Windows can do it, what would make you think Linux wouldn't be capable of it?

Things like CD_ functions are very specific to the device.

Yes, but here is the thing, they already had the code for all of it written, so throw all that code into a prepackaged extension, then nobody would fucking complain. And just tell people the extensions are unlikely to be continuously developed unless needed.

I personally enjoy 2D games when done right and I think that is what GM excels at.

Right, but that does not mean you need to break its legs off like Nvidia does to their Linux drivers to make them as shitty as they are on Windows.
http://www.tomshardware.com/news/nvidia-linux-basemosaic-ubuntu-parity,24519.html

Also as for the Windows cursor functions not being used, I see them being used quite a bit, and TKG specifically asked for that function when it broke, those were pretty well used.

most of the other window_* functions are still there at least and they only work on desktop platforms.

Nononon what are you talking about? That is not what I said at all, those are very usable functions.

Also, TKG, everything else you said I 100% agree with.