lordexod

vim file works with any path, not only "user.lib\macros".

XMacro.xnode - is the engine of the vi macros.

VI Macros (VIM) supports "XMacro.xnode".

This is the main layer of native xnode, and everything is supported.

It doesn't mean, that everything must be made available in xnode.llb.

These are correct.
XNodeAbilities.txt

I don't know which you have a version of labview, but on labview 2014 all works.

LVClass.vi

Works without xnode license.

XNode.zip

This is interesting, Ability, Method and Property Folder in XNode:

"NI" probably also to develops XNodes or XClass (XNode + Class).

You can always change the version.

NewXNode_v2.vi

Can bypass this detail.

NewXNode.vi

So if I get an error in "APP:XNode.Create", what am I missing?

XNodeCreateError.png

//Mike

 You must have a license.

It already exists, is called "function blocks" http://zone.ni.com/reference/en-XX/help/370622M-01/TOC26.htm , which are created using the "FB Core.xnode"

Can use "wim" file format

https://technet.microsoft.com/en-us/library/cc749478%28v=ws.10%29.aspx

Software "Imagex.exe" .

https://technet.microsoft.com/en-us/library/cc507842.aspx

WIMGAPI - wim api.

https://msdn.microsoft.com/en-us/library/windows/desktop/dd851918.aspx

https://msdn.microsoft.com/en-us/library/windows/desktop/dd834964.aspx

Object Manager tags list (*.rc and *.rch file tags).

objmgrtags.txt

I know I can do better this editor.

This is just a simple example of such a editor.

Maybe some of you will do this editor better.

Resource Editor.zip

Need to add plugins of resource tag names "New Plugin.vi"

FPGA component consists of two parts.

1. Normal XNode, ExternalNode, VI.

2. Module Generator "ModGen", config file: *.mgn, ModGen SDK: vi.lib\rvi\ClientSDK\Core\ModuleGeneration.

subpanel.vi

plugincontrol.vi

All methods and properties.

ms_and_ps.bin.txt

Mwuhahahahaha! Three config tokens have escaped your grasp! I modified them specifically for folks like Flarn! They don't appear as plain text anywhere in the EXE (or in any VI for that matter). Do they guard any great secret of LabVIEW? I'm not telling! But you can have fun pouring through the code and looking for interesting bits and trying to figure out what you need to put in your config file. LabVIEW 2013 or later. Good luck.

You're talking about this?

STR#_11400.bin.txt

Download, save on disk and run.

FGetSpecialDir (type [hex] 0x13)

FGetSpecialDir.vi

PlugInControls__packed.vi

This looks like "Botnet Abstraction Layer". :D

Why immediately just shy?

My english language is poor.