Problem Description

Unable to toggle off breakpoint on action once it's been moved into a triggered or looping event.

Attach a Capx

[attachment=0:8h8jj2lp][/attachment:8h8jj2lp]

Description of Capx

CapX is just a sprite with mouse click event to show off the breakpoint issue on the event sheet.

Steps to Reproduce Bug

• Set breakpoint on an action
• Move that action (with breakpoint) under a triggered or looping event

Observed Result

You lose the ability to turn off the breakpoint and instead get a "Cannot set a breakpoint here" warning. You are then forced to move the action out of the triggered or looping event in order to turn off the breakpoint. Then you have to move it back in. This is just an annoyance as I don't believe the breakpoint actually works but a bug nonetheless.

Expected Result

Couple of ways to fix this.

Option1: It could throw a warning and not allow me to move the action in until I've removed the breakpoint.

Option2: It could allow me to move the action in but afterwards allow me to remove the breakpoint manually since it's not supposed to be there in the first place.

Option3: Automatically strip out the breakpoint when I move the action into a triggered or looping event.

Operating System and Service Pack

Windows 7 SP1 x64

Construct 2 Version ID

Release 185 (64-bit/Steam)

Irbis - I agree with you 100%. I'm a noob and still have my Construct training wheels on. I went in with the same expectations you had...the layout and all layers on said layout would be reset to they're original state. I'm using a number of layers and finally realized it wasn't resetting them back to the initial visibility.

I don't mind if the product isn't updated but I would really love to see a note on this behavior in the manual. It isn't mentioned on the layout, layers, or system actions pages. It really makes the most sense on the system actions page since that is where 'go to layout' and 'restart layout' are mentioned. Neither of which reset back to initial visibility of layers.

Right click your My Documents folder and choose properties. There should be a location tab. On the location tab you can modify the location of My Documents. I have my pointing to the W drive which is mapped to a network share.

Problem Description

When going to "Open Project" from the start page or File > Open Construct 2 crashes with a "has stopped working" message. Here is a small excerpt from the event logs.

Faulting application name: Construct2.exe, version: 2.0.0.0, time stamp: 0x53f394a1
Faulting module name: SHELL32.dll, version: 6.1.7601.18517, time stamp: 0x53aa2e07
Exception code: 0xc0000005
Fault offset: 0x000000000019e877
Faulting process id: 0x9f4
Faulting application start time: 0x01cfd7bffecce0ac
Faulting application path: D:\Program Files (x86)\Steam\steamapps\common\Construct2\Construct2-Win64\Construct2.exe
Faulting module path: C:\Windows\system32\SHELL32.dll[/code:tymktegh]
[b]Steps to Reproduce Bug[/b]
[ul]
    [li] Step 1 - Redirect your My Documents folder to a mapped network share.  In my situation the W drive which maps to my NAS.
    [/li][li] Step 2 - Logoff and log back in again to Windows.
    [/li][li] Step 3 - Launch Construct 2 and go to "Open Project" on the start page or File > Open.[/li][/ul]
[b]Observed Result[/b]
The application crashes after step 3 above.
    
[b]Expected Result[/b]
Construct 2 should not crash and instead open up the open file dialog as it normally would.
   
[b]Operating System and Service Pack[/b]
Windows 7 SP1 x64
    
[b]Construct 2 Version ID[/b]
Release 178 (64-bit/Steam)

[b]Troubleshooting Performed[/b]
This issue is related to folder redirection of the My Documents folder to a network share.  Possibly related to a custom folder (or folder namespace?) in the Open dialog's navigation pane titled "Construct 2 game creator" which points to <My Documents>\Steam Cloud\<username>\Construct 2 Free.

[b]Workarounds[/b]
[ul]
    [li] Disconnect the W drive (redirected My Documents).
    [/li][li] Redirect My Documents back to a local path and logoff and log back on again.[/li][/ul]
Neither of the workarounds are ideal.  Especially in a networked environment with centralized storage.  I'm hopeful this issue can be addressed.