All of those you mentioned cannot be classified as "C++ development studio".

I have Visual Studio 2005 Pro from university. Don't own any though.

It's technically possible. Canvas object allows to do basic painting operations, and Image Manipulator object can save/load images to files.

Solved.

In casy somebody asked:

You put "pRuntime->AddDebuggerItem" into ExtObject::DebuggerUpdateDisplay method

And write:

if (label== "Hi-Jump Available")

hiJump=iValue;

In ExtObject::OnDebuggerValueChanged method

How to add Runtime Object's fields into Debugger?

There's a "pRuntime->AddDebuggerItem" method, but I'm not sure where to place it and what other actions to take to make some fields visible in Debugger's "Properties" (for example "Text Object" shows one property).

Thanks for quick bugfix ^^.

Thanks. That explains everything ^^.

There are several problems I'd like to clarify ^^. Working in C++ is really painful for me so tests would take hours ><'. You Devs probably know answer ^^.

1. Serialization order

Let's say I've fields: myVal1, myVal2 in EditObj, and fields: myFirst, mySecond in RuntimeObj. How should I do serialization stuff in code (serialization.cpp). Is this solution correct (treating 'ar' as stack):

/////////////////////////////
// RUNTIME serialization
void ExtObject::Serialize(bin& ar)
{
	if (ar.loading) 
	{
		ar >> mySecond;
		ar >> myFirst;
	}
	else 
	{
		ar << myFirst;
		ar << mySecond;
	}
}[/code:cwqirkhd]
[code:cwqirkhd]/////////////////////////////
// EDITTIME serialization
void EditExt::Serialize(bin& ar)
{
	int Version = 1;
	SerializeVersion(ar, Version);

	if (ar.loading) 
	{
		ar >> myVal2;
		ar >> myVal1;
	}
	else 
	{
		ar << myVal1;
		ar << myVal2;
	}
}[/code:cwqirkhd]

2. Passing values from EditObj to RuntimeObj
Created RuntimeObj stores handle to EditObj to have access to its data and stuff. Let's say I've two values in EditObj: myVal1 and myVal2. I want to make use of them during Runtime as well (by ACE Methods). Do I need to make fields "myVal1, myVal2" in RuntimeObj as well and duplicate data from EditObj in method "void ExtObject::OnCreate()", or maybe I can access EditObj fields from ACE Methods and not worry about making fields at RunTime Object?

3. Serialization in runtime
This question is somehow related to #2. Surely serializing object in Runtime is used for QuickSave/QuickLoad its state. When making QuickSave in runtime, does corresponding EditObj data serialize as well?

50 weapon with unique bullets, properties, logic and drawing routines? Even in programming language that'd be hard to maintain. Construct allows to organize objects in "families", you can think about it like a container of all instances of classes included within it (kinda "base class").

Construct eventsheets are based on events rather than scripts, I like actual functionality of it. Before getting into eventing you can prepare a pseudocode.

As for using methods I recommend getting to know "Function Object". It fully includes the idea of making methods with returnable value. Construct documentation describes it.

Try adding "play animation".

(Don't have access to Cons at the moment)

I don't know what you've posted, but have you thought about making a Canvas object with effect "mask"? That'd be good for pixel perfect map revealing.

These are available in pro version of Visual Studio.