nisystemsengineering / cef Goto Github PK

Better documentation on what folder glyphs should be located in (or an option to allow path to be specified for all glyphs in a repo)

Add comments/documentation that clearly explains that the Call Parent Node function must be called in the overridden To Repo function to maintain the recursive list.

For Unknown Menu Option, concatenate ItemPath to message so instead of “Unknown menu item”, message is “Unknown Menu Item: My New Menu Item”

IN the forum i added the steps:
http://forums.ni.com/t5/Development-and-Deployment/Configuration-Editor-Framework-CEF/m-p/3027441#M117

Arron mentioned this about it:
Built Exe problem – I know you posted on this in the CEF forum, but your solution did not work well for me and is it radically increased build times and resulted in large numbers of extra external files. Instead, I modified the FilePaths.vi to use slightly different pathing in the exe and so that the classes could be built into the exe file. I realize this would not allow for dynamic addition/detection of classes, but I do not need it

Add a built specification for the project

NodeClass property returns , not <blah.lvclass>. If editor options subclass property is returned with <blah.lvclass> then the match in ValidDragDrop.vi fails. This match should be made more robust.

I think we should make this work just like the LV tools menu. Things can be added statically, but a section can allow users to only install the tools that they want to use, but still have easy access to them.

The older versions of CEF used GXML, but it was removed for a binary file in the example to reduce dependencies.
Need to updated documentation

If we don't want to ship an implementation of this we could still leave the option there, but we should at least display something to the user that indicates its intentionally left blank.

Documentation should state the folder name of the node classes must exactly match the class name (had a problem when my folder was named ResistorTests but class was ResistorTest

Basically allow us to concatenate all errors we catch during init or configuration and display all of them to the user. Hide behind a conditional disable token.

Unless I am mistaken, I believe it now installs more than 2 abstract LabVIEW classes for example.

Glyph text is case senstive but no error messages if the glyph does not existGlyph text is case senstive but no error messages if the glyph does not exist

Typo in block diagram of ..vi.lib\CEF_TreeControl\Repository\GetClassPath.vi "buidlign"

similar to tbdf
makes it easier to package/distribute classes. editor glyphs folder should be a default library sort of like lv icon editor.

default is xml
potentially fixed by #22

Typo in VI Description of ..vi.lib\CEF_TreeControl\Summary.vi

The forcing lower case in the vi outside the vi.

As the classes and Glyphs are dynamic, they must be added to the always include in the dependency. The complete procedure is in forum in this link:
http://forums.ni.com/t5/Development-and-Deployment/Configuration-Editor-Framework-CEF/m-p/3026991#M116

The advance project has a predefined repo. If it is inherited by a child repo the children has no access to the parent data.
Few functions that might be done by children are custom save, custom load, tools to import things in the repo.
Need to add basic functions to access the memory structure

Typo in VI description in ..Source\CEF Test\subVI\FileDialog.vi

For Unknown Menu Option, concatenate ItemPath to message

Error clusters in the In Place Element structures not wired, resulting in pop-ups.

..\LabVIEW 2013\vi.lib\CEF_TreeControl\Node\FromRepoCluster.ctl needs Description

A large portion of the VI's on this palette don't have VI Documentation. We are using these in the Top-Level TBD examples, so the documentation will be front and center.

..vi.lib\CEF_TreeControl\GlyphIndexPairs.vi enum control should be labeled as Action rather than Enum

MIght need to check where are we calling dialogs and just have a single place to call them

cRIORepo Class has default class icon rather than a specific icon

for the other project using CEF I'd like to be able to get a reference to my parent node. This would allow me to inform that parent node I exist. Currently there is no way to do this until initialize returns because thats when you link them together by default. Is there an appropriate way to do this? If not, can I change the "add node" function to provide the parent ref by default?

Errors for the CEF will should be using the range : 538500 to 538550

@becega @Beazurt

In discussions initially we thought UID could be a static identifier but we should still ensure that the alias is unique. Thinking about it some more, we realized that if the user needs to identify a component by a unique name they always have the option of planning ahead and naming things correctly. We don't really need them to be unique because anyone who does need a unique alias will have to plan ahead anyway.

We should however have a right click option to show the GUID:
#30

The 'Configurator' text also doesn't move with resize. If we aren't showing users how to properly resize their plugins, I think we should turn off resizing altogether and document why. If we want to allow resizing, we should at least set a reasonable minimum size and make sure everything fits and moves properly inside of that minimum.

Glyph text is case sensitive but no error messages if glyph not found.

XML function takes forevvvverrr;
replaces:
LabVIEW-DCAF/TagEditorCore#89

A hashtag or other documentation showing a user how to create/replace the DVR typecasting constant in the VI would be useful.

Right-clicking a node in the tree and selecting 'View Node Data' for a group, current channel, and voltage channel, returns an error.