Good find, be sure to report it on the official bug list:

http://sourceforge.net/tracker/?group_i ... id=1003219

1987099 Deleting Event Sheet crashing contruct

The following crashes Construct on my system:

1. Create a new project

2. Add a new event sheet

3. Open the new empty event sheet (if you don't open it before deleting it Construct will not crash)

4. Click on Add/Edit Event Sheets in the Applications properties inspector

5. Select the newly added event sheet click the red X button to remove it

6. Click on the Done button and on my system you immediately get a crash

1987087 Transitions crash application when restarting current layout

Transitions work fine when going from one layout to another different layout. But when going from the current layout to the same current layout in order to restart it they crash the application. I've attached an example that has a successful transition followed by a crashing transition (see bug tracker).

Here is a list of bugs I reported in separate threads before I began this list:

1987077: On Animation Finished event not working

1987075: Every X milliseconds always triggered at start of layout

1987074: Layout end and Application end events not triggered

1984964: Recent Documents list is showing duplicates

I'm going to keep track of all my bugs in this single forum thread. For each bug that I find I will first add an entry to the official bug tracker on SourceForge and then add a post to this thread.

It's good to know it helped save you a few hairs

As awesome as Construct, is it is still beta software so what I have found very helpful is whenever something very strange happens or doesn't work as I expect it I quickly create a new project and make the simplest possible layout that tries to reproduce the problem. If I can think of some work arounds I'll also try those in my simple test case. Then when I'm done I make note of the problem and add it to the bug tracker at source forge and report it here as soon as I get a chance.

I just added this to tracker with an example cap.

Snoop

I've added these two bug reports to the tracker. I've included a sample cap that reproduces the problem in a simple scenario.

I'm trying to understand how behaviors and events interact with one another. I've noticed while playing around that if I add behaviors having to do with movement and then try to tweak aspects of the sprites positioning it leads to conflicts. A simple example of this is the following:

Add a sprite to an empty layout, give that sprite the ball behavior and turn on "Rotate Object" ball property so that when the ball sprite hits a solid wall it will rotate on bounce. Add solid wall objects for the ball to bounce off on the borders of the layout. Now everything will work fine in this simple example. But try to add an event that updates the rotation of the ball sprite and it will not rotate unless you turn off the "Rotate Object" property. I wanted the ball to rotate between bounces but to my surprise it ignores all changes made to it's rotation during an event and only rotates when the behavior's built in functionality tells it to (ie. every time hit hits a solid wall).

Could someone explain to me at a technical level why the system works this way (I'm a software developer so you don't have to simplify things). Is the behavior implementation running after my events and overwriting my changes? Could behaviors run before my events so I could tweak their results in my events? Or are behaviors able to make certain object properties read only? How are user events and behaviors inserted into the game's main loop.

Thanks,

Snoop

As a work around you may be able to use JoyToKey during initial development:

http://www.electracode.com/4/joy2key/Jo ... ersion.htm

Wow that was quick . Thanks Ashley!

Enjoy your well deserved holiday Ashley!

Cheerio!

Snoop

Great, you read my mind . I'll be sure to lump my suggestion in one thread for easier management.