Maximize on Play Error with Actions panel open

[qholmes]

In my Layout config that i use for playMaker i have the Actions panel set to be under the Inspector on the right side..

If i set Maximize on Play on then i get NullReferenceException:Object reference no set to an instance of an object
UnityEditor.DockArea.OnGUI()

If i switch to another layout it works fine and if i just close the Actions panel it works fine too..

Q

[Alex Chouls]

If you get a chance, can you see if this still happens in Unity 3.4 with your layout? Couldn't reproduce it here, but I'm not sure if I have the same layout...

[qholmes]

I have not tried it since but i just did and yes i do still get that error... I added another monitor to my set up so the game window just sits over there now... i can send you a screen grab of my set up if you like. or there are layout files too are there not? would that help?

I have not installed the latest Beta you sent me yet.

Q

[qholmes]

Once i got into this i could not get out of it... i tried changing layouts over and over and got into a state where i could not play anymore.

Failed Repaint or something.

I closed Unity. Just waiting for it to start up again. See if it works.

Restarted and now it works again.

Q

[Proton]

Strange bug, I was able to reproduce it with this setup in the attached image.

That is the standard unity 'Wide' setup with only playmaker 1.1 added.

Four things I noticed.

1. Once you get into this state, you can't get out without changing the layout.
2. The 'Actions' tab needs to be it's own window. If you make it a sub-tab like how the main 'PlayMaker' one is in that screenshot, the errors will not appear.
3. It needs to be below the 'Projects' tab for the problem to happen. I put it beside the projects tab by itself, but it didn't cause the errors (this one is strange).
4. If you open the 'Actions' window but don't dock it anywhere (leave it floating), it disappears. Perhaps this is normal, but seemed suspicious.

[qholmes]

Here is my layout... i remember from before that it had to do with the Actions window for sure...

Q

[Alex Chouls]

The Unity 3.4 update should have fixed this... can you confirm?