You could try to rename the UI classes of the Vuforia samples, as suggested in that thread; this could be a bit tedious, but would solve in the meantime...

Hi NalinS,

Thanks for the heads up, however I can't update until the issue with namespace is solved I am having to stick to an older version https://developer.vuforia.com/forum/unity-3-extension-technical-discussion/287-namespace-conflict-ngui

Thanks

S

If you download the latest UDT sample for the latest SDK you will find that it is much streamlined.

Maybe this could help you?

N

Was a work around ever found for this issue? 

I'm also working with NGUI and want to bypass the default GUI actions and buttons. 

By default my NGUI UI Root works fine, an extra buttons which is setup to take screenshot works and ignores the NGUI layerm, but the standard UI still remains in the shot. I believe the answer is related to this thread. 

Hi - thanks for your reply. 

I'm new to C#, so still getting up to speed with its concepts. 

As I understand the added value of the image-quality-brackets, I wouldn't mind (or actually, would be happy) using these. 

So to narrow down my question; I would like to know how I can replace the images used in the sample GUI with buttons I created with NGUI (which are basically game objects which have a void OnClick event). Reason being my existing GUI - which already takes care of all screen scaling - interferes with the one from the example. 

Or to put it in another way; how would I fire the buildTarget action (e.g.) from outside the existing UI script. 

I'm guessing it is something in the area of 'return ButtonID.BUILD_TARGET_PRESSED' within UserDefinedTargetBuildingUI, but it's all so intertwined I'm struggling a bit to find the exact location to tweak this (without breaking anything). 

I realise this might be a bit of an exhausting question, so please do let me know if I need to specifiy further. 

Thanks again, 

Control of the scanning state and target building is demonstrated in UserDefinedTargetEventHandler.cs. This is also where the UserDefinedTargetBuildingUI and ScanModeUILogic are instantiated, and where you can disable them, though it could be helpful to adapt ScanModeUILogic rather than remove it as it provides useful methods for handling changes in frame quality and also UI states.

The thing to keep in mind regarding UDT is that it requires that the quality of the captured camera frame is sufficient to generate a trackable target image. It will reject inviable target images. So your UI logic needs to accommodate changes to the frame quality, which are provided through a callback ( OnFrameQualityChanged(ImageTargetBuilder.FrameQuality frameQuality ). This is what's demonstrated by the white -to- green corner brackets.