Nifty XML Autocomplete Problem

In the process of writing some NiftyGUI video tutorials (still writing the preparation code atm) but I can’t seem to get the XML autocomplete to work properly. It works for screen elements and partially for layer elements (attributes work but only 3 inner elements pop up), but most elements inside layers such as panel etc… don’t work. Just wondering if anyone else has this problem, or if i’m doing something wrong, thx. Heres a vid:



http://www.youtube.com/watch?v=pS7T7pZwhYA



Searched for it, the only things I found were:

“i cant figure out why everyone uses xml, it has no syntax correction or auto complete funktion or anything, so why”

http://hub.jmonkeyengine.org/groups/general-2/forum/topic/how-to-initialize-appstate-together-with-screencontroller/#post-170043



“- In Netbeans, the xml autocompletion using the schema works up to the layer tag. Do you have any idea why?”

Void256: Nope, no idea. I’m using eclipse :stuck_out_tongue:

http://sourceforge.net/projects/nifty-gui/forums/forum/807893/topic/4516508

Yeh, I always assumed theres some quirk in the schema file… Maybe the wrong one is referenced? I don’t know really, the platform does this automatically based on the schema file referenced in the XML header.

1 Like

I get the exact same problem and I think it’s something to do with the xml schema file. Because the nifty attributes are very fluid things start falling down.



A bigger problem is that if you include nifty stylesheets/etc then the graphical preview thingy immediately falls over.

1 Like

tried in vanilla Netbeans 7.1.2 and the jME SDK RC1 and it has the same problem

just downloaded Eclipse and it works in there fine, grrr :frowning:

That’s a clue though, might be worth investigating the difference between the netbeans and eclipse implementation of that. Could also see if there is an alternative XML editor for netbeans that we could replace the standard one with and which copes with the problematic XML…

Its a scheme issue, just have to know what issue… Eclipse famously run broken projects, so why not use broken xml schemas? :wink: