Jump to content

Neil Pate

Members
  • Posts

    1,185
  • Joined

  • Last visited

  • Days Won

    110

Everything posted by Neil Pate

  1. Champions access only (things like this make me sad...)
  2. Ok so lets try and make this as simple as possible. Imagine all you have is a single constant value of your International thankyou enum on your block diagram. I get the feeling you would like to display this as a 2D string array with the first column listing all the possibilities of the enum and the second column has "1" in the column of the row that matches the constant value otherwise it has a 0, is this correct? Can you describe in words how you would create this array?
  3. Ignoring the fact that your array is not doing anything at all (you could just wire the Array indicator straight to the Strings[] output) you said you wanted to show the value as well, with 0 or 1.
  4. I have given you my advice. Try implementing it as a 2D string array first. Leave the tree out of it.. Once you have mastered that you can think about getting it working in the tree. As I said way earlier on in this thread I really think you are "mixing methaphors" here. The cluster viewer displays the "values" of items in the tree, not the set of all possible items. If you want that you are going to have to add it yourself and the tree API is not pleasant to work with.
  5. You need to learn to crawl before you can walk... perhaps somebody in this forum will just show you the answer you are looking for (i.e. do your work for you). I am not that guy though, sorry.
  6. Thanks Yagnik. The tree control is not a nice thing to work with, I fear you are trying to do too much at once. I think perhaps you need to start off a bit smaller. If you really really want to include the enum items in the table first try and get it working as a 2D string array. I mean not using any of the code you have been, just by figuring it out yourself. You can achieve what you want with a single enum and a nested for loop. Once you have that working you can figure out how to get that integrated into the cluster viewer code you have.
  7. Yagnik, anything is technically possible as you have all the source code. What you propose just removes the need for the nested loop as you then have the elements already in the cluster. Out curiosity, what is your exposure to LabVIEW, I mean how comfortable are you with the language?
  8. Why are you changing the OpenG VIs? Those are meant as external libraries and should not normally be altered. If you really want to make some changes to one of them, make a copy, give it another name and then change that one.
  9. ok, I understand. So when trying to present the enum in the tree you need two loops. Loop once over all the possible strings, and inside this loop again over all the strings and write them as simple items.
  10. Sorry, I still don't get it... The Config cluster is your process data, ok that makes sense. But an Enum is only a single value, it is not multiple values, why are you trying to display it as multiple values?
  11. I still don't get what you are trying to achieve. Why do you want to present the different enum possibilities in the tree, what do you plan on having in the value column for these elements?
  12. I didn't say it was going to be easy... Can you not iterate over the Enum strings and just insert them one by one using the Parent tag?
  13. Yes sure it is possible, you need to modify the case structure and handle an enum slightly differently to other types.
  14. Yes, that is what I suspected you wanted. Do you understand what the rest of the code is doing? It is displaying the value of each element in your clusters/arrays, not the possible set of values... All you need to do is make an array or cluster with one element set to each value of the enum.
  15. smithd, Ton's variant probe is great but does not do any more than the Cluster viewer class at the OP included. His question was related to the desired to display enum values as children and not in the value column, and I am trying to understand why this is desirable as an enum is not a collection of values at runtime (like a cluster or array).
  16. OK so that is better, although still I would ditch the OpenG directory and just install them properly. So I don't really understand your question. The Tree is a representation of your cluster, the hierarchy of the tree (parent/child relationship) represents the nested clusters and values. The value column shows the actual value of each element, this appears to be working correctly. What are you trying to achieve? Can you post a screenshot of what you would like to see?
  17. Your zip is all messed up, so many dependencies in the wrong place etc. Take a look at the Files tab in your project to see where all your files are. You need to include everything not in the LabVIEW directory if you want somebody else to check it out. Also, why are your OpenG VIs not inside the LabVIEW directory?
  18. I have nothing substantial to add other than I also added my calls inside conditional disable structures which I never in the end bothered to disable as performance was way in limits. The calls themselves are quite lightweight I think.
  19. Bump to this thread. I really do not like mutation history being stored. I have a stupid LabVIEW bug where the IDE thinks I am using a class which I am not (really am not). I thought perhaps it was being referenced from the class mutation history. So I poked around in the history of some of my classes and am horrified at the history that exists! I don't know about others, but my standard framework has been adapted over time (several years for my current actor based framework). I still have references in the mutation history for application specific classes from my original project! Urgh... I suppose I have no excuse, I have known about this "feature" for a while, but it is easy to forget about.
  20. Rolf, sounds like a great idea. I love those VIs but yes they can be on the slow side. I would happily accept the trade-off of >= LV2012.
  21. works for me.
  22. This is a little different to, say, LabJack; this fools the Xilinx compiler into thinking that the "standard" work-flow is being used. There could be some license agreement behind the scenes between NI and Xilinx that we do not know about.
  23. I think perhaps we have a different definition of the word *any*, but I do not wish to take your thunder away. This is very impressive what you have managed to create, clearly a lot of work has gone into it. I seem to recall seeing something like this a few years ago? This is almost certainly a non-NI sanctioned product, are you aware of any legal ramifications of piggybacking into the toolchain? What I mean is, if we have a valid FPGA Toolkit license is this actually legal? My Chinese is not so good, so the website is not much help. Do you have pricing information? Also, the Atom-RIO looks very interesting, I presume it is like a cRIO type clone?
  24. Absolutely. My top-level main GUIs are entirely static with regards to what "views" can be loaded into the main subpanel. I can only shudder to think how complicated this would all get if everything (including every single scrap of business logic) was "templated".
  25. Huh? You ask a question and then answer it yourself. Have I missed something here? Can you share with us how you can target any Xilinx FPGA?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.