Playmaker Forum
Bug Reporting => PlayMaker Bug Reporting => Topic started by: zelmund on January 28, 2016, 06:08:09 AM
-
started by this tutorial and noticed that after attaching playmaker UGui component proxy i git this error: "UI Target is not a valid UI component"
what i should to do?
working in unity 5.3.1 with playmaker 1.8
-
its working with toggle ui
but button is dead for some reason
maby its a naming convention somewhere?
-
anyone got this problem? cant fix it still :( project stuck
-
any news about proxy?
-
Hi,
It works here, on all versions I tests and work with, the screenshot is from 5.3.1 f1
(http://i.imgur.com/0OrW43A.png)
Can you start a fresh project, with just playmaker and uGui package and see how it behaves?
Bye,
Jean
-
ok. it working on Unity 5.3.2p1 with PM 1.8.0 rc41
testing in project now.
-
tested in project... not working. maybe i deleted previous version not correctly? i deleted all playmaker files and reimported it, but useless.
-
Hi,
ok, this is 5.3.2 so maybe there's a change in that version, I only have 5.3.1
check back on 5.3.1 and let me know. meanwhile I'll install 5.3.2 ( will take time, not before tomorow, my connection is slow...)
Bye,
Jean
-
it happens from 5.3.1f1 to current patch. checked it while we did upgrade project.
cant do screenshots with that but, because i need to convert all project back to that version. project is very heavy (around 70 gigs).
but again. its ok in clear project. all works fine.
dont understand what can affect on playmaker that can brake proxy.
-
Hi,
The proxy is not related to PlayMaker directly, I am not sure what can cause the proxy to fail to catch a Unity UI Button...
like so:
(http://i.imgur.com/i7DB2gT.png)
Bye,
Jean
-
yes. that what i saw in unity4 some time ago. will try to import in clear project some tools from main project. will see what happens and when it will broke.
btw, i opened plamaker UI changelog, version is 1.1.3, is that correct?
-
Hi,
it should be 1.1.4 but it won't make a difference for your problem I feel.
Bye,
Jean
-
hi again.
yesterday i had some strange warnings from playmaker. something about reflections. cant repropduce it now, but seems our own scripts and dlls causing problems. our programmers blaming everything exept their code (because they are programmers...). but maybe you can tell, could it be problems with reflections in code?
-
Hi,
could be that they created a "Button" class and it clashes with UnityEngine.UI.Buttom class.
but it's unlikely, I am puzzled indeed. I am not too sure however if you tested this in a clean project, because you mentionned your own scripts.
Bye,
Jean
-
i suspect the same about button conflict. will try to get this info from programmers.
-
i found the problem by deleting scripts. will try to explain.
we have a script with this stroke:
public class Button : MonoBehaviour, IDigitalInputDevice{.....
and your script PlayMakerUGuiComponentProxyInspector.cs have this stroke:
if (_target.UiTarget.GetComponent<Button>() != null)
our programmers said that proxy will not wok because of namespace. so we need to change in plamaker script this:
if (_target.UiTarget.GetComponent<Button>() != null)
to this:
if (_target.UiTarget.GetComponent<UnityEngine.UI.Button>() != null)
then doesnt matter who will add any classes with same name, your proxy will work in any cases.
what do you think about it? i tried this option and its finaly woking now ;D
-
we have a script with this stroke:
public class Button : MonoBehaviour, IDigitalInputDevice{.....
This script should really be using a namespace. Button is too generic to live in the global namespace, it's only going to cause more problems down the line...
-
Hi,
Yes, Typical names like Button will always be tricky to handle.
I will change it on my side, but As Alex said, I strongly suggest you also create your own namespace for your project's specific classes to avoid clashes with other assets.
Bye,
Jean
-
im not programmer myself, but i dont understand why our programmers not using their own namespace also.
i will ask them about it too.