Playmaker Forum
PlayMaker Help & Tips => PlayMaker Help => Topic started by: kitheif on June 11, 2014, 02:00:42 AM
-
Ever since the new update for Playmaker I have not been able to use Playmaker with Probuilder. :'(
Assets/PlayMaker/Editor/FsmEditorWindow.cs(72,30): error CS0246: The type or namespace name `AboutWindow' could not be found. Are you missing a using directive or an assembly reference?
-
Hi,
Can you fill out a bug report in "PlayMaker/tools/Submit But Report" so that we can keep track of this. Thanks.
Bye,
Jean
-
After talking to the guys over at Probuilder, it looks like they've fixed the issue and the latest versions do not give this error anymore.
-
I just got this error, latest install of probuilder installed onto latest version of playmaker. I just emailed them.
-
I just got this error with latest Playmaker & latest ProBuilder, ProGrids.
(Playmaker 1.7.7f6, ProBuilder 2.2.5f5 v2341, ProGrids 2.1.3 v2464)
and solved this problem with renaming(refactoring) some classnames on Playmaker itself.
At first, I examined all sources and found it's not caused by them.
All of their ProCore window sources is already started with 'pc_'...
and when I caught by this error, the corresponding Playmaker source -
Playmaker/Editor/AboutWindow.cs was strangely disappeared.
- - - - -
Well then,
First I made a clean project and installed Playmaker only.
Then I just temporarily renamed some 'too familiar' classnames
that cause conflict now, like :
(Actually, It's a refactoring in MonoDevelop.
It renames not only the classname itself, but all of references and class filenames.)
AboutWindow -> plmk_AboutWindow
ContextToolWindow -> plmk_ContextToolWindow
ReportWindow -> plmk_ReportWindow
(I think this prefix is better with 'PlayMaker...' or something,
however I'll leave it to Hutong.)
Finally, I imported all the ProCore assets i need. (ProBuilder, ProGrid, etc.)
It works well, and I'm using all of that with no errors.
Hope this helps.
ps:
Dear Hutong,
Please refactor all that 'general, familiar classnames' at next release
to avoid future conflicts...
Thanks in advance! ;-)
-
Good catch! Most classes in Playmaker are in namespaces, but Unity 3.5 didn't support namespaces for EditorWindows. Most of the EditorWindows are named better, but indeed AboutWindow was a poor name choice!
Anyway, the next version of Playmaker will drop support for Unity 3.5, so we can put these EditorWindows in namespaces. For example:
// (c) Copyright HutongGames, LLC 2010-2014. All rights reserved.
/* NOTE: Wrapper no longer needed in Unity 4.x
* BUT: changing it breaks saved layouts
* SO: wrap in namespace instead (supported in 4.x)
*/
// EditorWindow classes can't be called from a dll in Unity 3.5
// so create a thin wrapper class as a workaround
namespace HutongGames.PlayMakerEditor
{
internal class AboutWindow : AboutPlaymaker
{
}
}
These changes should work now if you're using Unity 4.x. I'll try to upload a patch so you don't have to hand edit these files...
-
So what to do with this ?
// (c) Copyright HutongGames, LLC 2010-2014. All rights reserved.
/* NOTE: Wrapper no longer needed in Unity 4.x
* BUT: changing it breaks saved layouts
* SO: wrap in namespace instead (supported in 4.x)
*/
// EditorWindow classes can't be called from a dll in Unity 3.5
// so create a thin wrapper class as a workaround
namespace HutongGames.PlayMakerEditor
{
internal class AboutWindow : AboutPlaymaker
{
}
}
also having this issue, so in order for my playMaker to work, i just run a
older version, then everything is fine. Only have this problem with the new version.
-
Hi, struggling with this as well.
Where can we get mentioned patch? I'm updated on Unity Asset store to 1.7.7.f6.
-
Same here -- I've got the latest versions of Playmaker and Probuilder, and am getting that error:
Assets/PlayMaker/Editor/FsmEditorWindow.cs(72,30): error CS0246: The type or namespace name `AboutWindow' could not be found. Are you missing a using directive or an assembly reference?
-
Hi,
The Version Alex is mentioning is still in beta, so are you sure you are using the latest version of pro builder, if you have ( please double check :) ) then I'll get in touch with pro builder guys to test it locally and explain how to fix it.
Bye,
Jean
-
yes, I downloaded the latest version before trying it with Playmaker. So any tips would be much appreciated.