I doubt this is the case, but I thought I would check to make sure.

They sort of do. Use pick by comparison: distance(.x, .y, otherobject.x, otherobject.y) is less than however many pixels.

now rotated objects overlap when their rotated bounding boxes overlap

AWESOME. Been wanting this feature for a while! Is it as fast as normal box collisions, or is it somewhat more computationally intensive than normal box, but still less than per pixel?

I sometimes get an error:

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

Construct 2 Check failure

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

Check failure! This is probably a bug:

No system expression found when evaluating identifier

Condition: system_expression != NULL

File: Projects\ExpTree.cpp

Line: 657

Function: void __thiscall ExpIdentifier::Evaluate(class ExpResult &)

Build: release 36 (32-bit) checked

Component: Construct 2 IDE

(Last Win32 error: 0)

I'm having difficulty reliably reproducing it, but it happens often. It seems to happen when setting a text object's text to a local variable. It also happens sometimes when dragging actions/events. I saved after getting the error here, the error shows on opening the file: http://www.amirai.net/forums/error.zip

Then after ignoring the above error and moving stuff around the event sheet, I got this error, which might not be important since it only shows up after ignoring the previous error, but I thought I should mention it anyway just in case:

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

Construct 2 Check failure

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

Check failure! This is probably a bug:

Creating deleted status undo point with no elements

Condition: !project_elements.empty()

File: Undo.cpp

Line: 75

Function: __thiscall ModifyDeletedStatus::ModifyDeletedStatus(const class std::vector<class ProjectElement *,class std::allocator<class ProjectElement *> > &,bool,const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &)

Build: release 36 (32-bit) checked

Component: Construct 2 IDE

(Last Win32 error: 0)

Enjoying the rapid updates!

Sorry, I'm a little confused. Do you mean variables declared at root scope become global for the event sheet, then they disappear when switching to a layout that doesn't use that event sheet, or do you mean they become the exact same as global variables, with persistent values and are accessible even when going to a layout without the declared variable in the event sheet?

Yeah, I guess it sounds fine since a hash table is so close to the same thing if I want persistent variables. Also, good point Aeal.

Hmm... perhaps a 'retain value/reset value" parameter?

I'm not sure either. One benefit of doing it this way over normal globals though is they can be created dynamically at runtime. I personally would like the option for them to be able to retain their values, but if not, I can continue using a hash table for that instead. Either way, looks handy!

One other thought, I assume the syntax checker will properly know if a local variable is currently usable/within its scope or not?

Do the variables and their values only last one tick, or do they remain for multiple ticks? I think they'd be far more useful if they would last for multiple ticks.

I understand that float accuracy is always an issue, but I thought floats could hold absolute 0's

As far as I've heard they can't.

Oh, sorry, misunderstood. Not sure how to do that.

Right click on the bar above the color, select use expression, then use rgb(r, g, b) with r, g, and b being values from 0-255.

I thought in CC upon pressing 5 would place the hotspot at the closest integer pixel to the center, not placing it at a subpixel?

Since C2 has no hotspots yet and I assume is mathematically calculating the center, perhaps simply round that number then?

Stuff that can't be easily worked around should be first in my opinion, like families, global variables and fine collisions. But I want event groups anyway.

And good on ya Davo!