Maybe if you do add it, a pop-up balloon could appear, explaining that?

You could also make a solids family and check for collisions with that.

I miss these too. And pick by comparison.

Ashley Yeah I almost posted it as a feature request a while ago, and then I was like "Wait a - IT'S ALREADY THERE!"

Happy birthday! That's an amazing amount of progress for one year!

Maybe I'm missing something - couldn't you just set the solid enabled property to disabled?

But there will be a way to group different objects, right?

I can think of a couple situations in which that'd be useful, such as when you want to create/destroy/rotate/move an entire composite object at once.

It would automatically associate all instances with each other (for instance, a condition that selects one object would include all objects of that group into the SOL).

That would enable things like a tank emitting smoke particles, complete with a main cannon and a machine gun turret, with a health bar and a player name (for instance).

Fimbul

What you want and are describing are containers, which are on the to do list. Or the pairer object, which can make containers at runtime, though that also hasn't been implemented yet.

Well, that's why I included this part too:

- if we're busy it may take a couple of days to get round to the report. We're on it though!

So no, don't assume it's been forgotten, it's only been 2 days! I also don't mean to imply you're being rude, I'm simply stating you should wait a little longer before assuming it's been forgotten about. Patience! :)

From the sticky:

- often we're busy, so if there's a short one-line answer asking to clarify, please don't think we're being rude, we're just trying to get to the bottom of it as quickly as possible.

- if we're busy it may take a couple of days to get round to the report. We're on it though!

- some bugs are much more difficult to fix than others and might take longer.

I know Ashley makes it look easy, but these things do sometimes take a while. :)

Confirmed on 32-bit vista as well. Steps:

Add sprite.

Add family, add sprite to it.

Add family variable.

Add sprite2.

Add sprite2 to family.

Click sprite2 in the project bar.

---------------------------

Construct 2 Check failure

---------------------------

Check failure! This is probably a bug:

No instance value for instance variable

Condition: i != instance_values.end()

File: Projects\InstanceVariable.cpp

Line: 176

Function: class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > __thiscall InstanceVariable::GetInstanceValueStr(class ObjectInstance *) const

Build: release 78 (32-bit) checked

Component: Construct 2 IDE

(Last Win32 error: 0)

Also got a second error after clicking abort:

---------------------------

Construct 2 Check failure

---------------------------

Check failure! This is probably a bug:

Object texture leak: a texture is still loaded when cleaning up an ObjectTexture, check all textures released properly

Condition: gl_instances.empty()

File: Projects\ObjectTexture.cpp

Line: 41

Function: __thiscall ObjectTexture::~ObjectTexture(void)

Build: release 78 (32-bit) checked

Component: Construct 2 IDE

(Last Win32 error: 0)

This is something where C2 and CC currently differ, but hopefully will be fixed soon. C2 runs some sort of a loop when collisions happen based upon the number of instances involved.

http://www.scirra.com/forum/r75-loop-apparently-running-without-a-loop_topic48141.html

1) SS? Do you mean CC (construct classic)? If so, you might have missed that there was a new version released today. :)

2) CC already has both an edit box and a list box, C2 has an edit box built in, and a list box as a plug in. I don't know what you mean by design object, as neither version has a design object.

3) If by SS you mean CC, they're working on it. Features take time to implement, and as such can't all be impremented immediately. Ashley's generally doing the more important ones first that don't have work arounds, like families.

4) If you mean export to android, C2 already can export to it with phonegap. I've read that appmobi is working on android support as well for improved performance.

As for getting CC to export to android, it's extremely unlikely. Difficulty exporting to other platforms was part of the reason why Scirra started over with construct 2.

If you meant porting CC or C2 themselves to android, for CC it's simply not happening, and for C2 it's an unrealistic task at the moment with Ashley being the only developer. Not only are there hundreds of thousands of lines of code to port as well as user interface changes that would have to be made, coding things for android is a very difficult task due to the incredible amount of software and especially hardware fragmentation between devices. Some of them don't even have floating point units! Porting something is not as simple as it might seem!