Hiho,

I'm just wondering, i wrote a little help in another treath ( here) and there was a "solution" in a file with the ending .c .. but i never worked with .c before..

now can i just include them? do i have to watch something special about it?

I am new to this programming stuff.. i actually begin from zero and i just used the GameStudio 7.5 and its Scripting editor SED 7.10.1 .. and now im wondering if the SED can also work with .c files?

u get my problem?

thx for help!

".c" files always contain "lite-c" code. ".wdl" files always contain "c-script" code or world definition language as it was called in ancient times. These are two different (yet very similiar) programming languages. SED won't care if you use lite-c or c-script. However, if you have a .c file it will always be interpreted as lite-c and .wdl files always as c-script. If you're new to programming i recommend choosing either lite-c or c-script and starting to learn it. My personal selection would be lite-c. It's more flexible and will be the future of 3dgs. If you're able to programm in lite-c you'll understand any c-sript code anyways.

You can include .wdl files in .c files but not vice versa and my personal recommandation is to never mix the two.

okidoki

good to know that i started with the "wrong" one so i have to learn about this lite-c..
thx thx

is the SED a good thing to learn lite-c.. or is somewhere out there in the unlimited space of the inet a better tool to work with?

It's not the wrong one. Lite-C is just more powerfull and the future of 3dgs. On the other hand you have a lot more possibilites in lite-c to mess things up. You'll remember these words next time you overwrite random parts of your memory or get somehow lost with pointers. ;-)


Give it a try. SED ist not the top of editors but sufficient for the beginning and has the advantage of displaying the helpfile directly. If you used SED for a time and find it doesn't fit your needs switch to another editor. You can use almost any text editor you like. However, sometimes you'll rely on SED, i.e. for debugging purposes.

Ok.. and which editor u use uhrwerk?

i mean, if i work now with SED, and im used to it.. its not hard to change for better purposes?


and other question.. can i make a .exe file with SED? or gamestudio at all? is there some tool for it included in GameStudio? i didnt find anything..

edith says:

i worked now with the .wdl script language... and now, that i heard that lite-c is "better" i wonder, can i somehow translate the .wdl's into .c's? is there a tool or something? or some "trick"

I use SED as well. Fits all my needs for writing c code.


For developing with java I use eclipse and netbeans. For developing with Object Pascal I use Delphi. While there are many differences in the comfort of these development tools the base functionality is always the same. You type some code, hit the compile button and that's it. If you've got a little more flexibility than the average 100 year old switching an editor is quite easy. If you got a drivers license you won't have problem driving a Toyota or a Chrysler. It's just a matter a comfort and personal preferences.


Yes, you can. That's called Publishing. Have a look in the manual under "publish".

what a nice support.

thx a lot!

That's one of the best things with gamestudio in my experience. The forum is a place where you can find answers to almost all questions and the community is very helpfull. There is always somebody helping you out, regardless of your skills or the complexity of your questions.


You can translate c-script into lite-c easily. It's mostly some keywords that have changed. Additionally lite-c is case sensitive and works with pointers. There is a page that describes the migration process from c-script to lite-c in detail: http://www.conitec.net/beta/litec_migration.htm You can also find this page in your manual.

I see, i see.. the community is very, very helpfull.. yesterday registered and a few problems solved

thats nice!

thx uhrwerk for the migration's page

Now i wonder, GameStudio is made for the c-script.. is it not somehow slower with lite-c? because its not supportet for it?

or do i something missing?