Jump to content

LogMAN

Members
  • Posts

    715
  • Joined

  • Last visited

  • Days Won

    81

Everything posted by LogMAN

  1. Turns out LabVIEW is connected to this forum. It has given me the right answer directly after my innocent question... The issues you described are exactly what happened to me today while changing a whole class tree, RIP project! Interesting point... I'll take that in mind for my future development. I always considered property nodes as a huge advantage over accessor VIs when it comes to large amount of elements (you know its small and tidy...). It seems there are some major drawbacks! The whole 'Error Cluster Everywhere!' story is also something I'm very concerned / confused about. In many cases I just have an error terminal going in-out with no particular meaning to my VI, just to maintain facade. Is it a way to get rid of the 'IDE slowing down' issue if I remove all the case structures from the property Read/Write VIs?
  2. Just tried, but unfortunately LabVIEW removes the colon Tried 10 times However I'm stuck with LabVIEW 2011, so maybe its a new feature? EDIT: Found a thread that describes what you mean: http://lavag.org/topic/13581-property-node-names/ Mr. Mike described how to do that >> Thanks man! The long name is what shows in the property selection menu (when you click on an item in the property node). This name is also used to structure that menu. If there is a colon in the long name, you'll get a submenu ("pull-right"). e.g.: If you had two properties with long names "Color:Foreground" and "Color:Background," they would both be in a "Color" menu listed as "Foreground" and "Background." The Long Name can be set in the editor by going to the class properties dialog (i.e. right clicking on the class and selecting "Properites"), selecting "Item Settings" and choosing the property you want to edit. The same for the Short Name. Set the Long Name with a colon and you'll get a nice property selection list! @shoneill: You're the best, thanks!
  3. There are of course numerous approaches and personal preferences to that matter, so this is how I generally handle it: First of all, each element of my class private data is accessible via property nodes, however there are some exceptions for arrays >> you can't have an index terminal on a property node Some of the properties are public, some are private, some are read or write only. However each property has a read and a write accessor for use by the class itself (no bundle/unbundle) All data that is absolutely required for the general function of my class is presented by member VIs. However you could use the public read/write properties to directly access data or get additional information if necessary and possible (remember some of the properties are private ). Also the member VIs do not necessarely just return the private data, but they return data in a way the developer can handle it (Trying to avoid complex clusters). If NI would allow us to create property node hierarchies and invoke nodes all the considerations would not be necessary... Just thinking about it makes me so You mind sharing your experience / knowledge? My applications are heavily based on property nodes and there is just one nasty issue I found up till now >> Property nodes are slowing down the IDE if they contain complex data (class, clusters).
  4. This tool is nice and will become very useful once the bug is fixed. I tried your code and instantly experienced the bug. However there is a workaround: Running the main VI directly from disk will prevent the crash. Sadly it will crash the moment you close the UI. I found one issue so far (seem to solve the problem for me): You store references to each library into a variant attribute that is collected in the Variant 'Reference Lookup List'. >> Remove all dependencies to that list and fetch the references again in your 'Callable Methods.vi'. In my case the Browser did not crash anymore... However that does not fix the issue with calling the Browser from the Tools menu... I don't know for sure, but it seems that the instance from the Tools menu compared to starting a VI directly from disk is somehow different...? Does anybody know more about that? EDIT: Tested in LabVIEW 2013 (32-bit) on Win7 x64
  5. There you are my soul... How dare you talk about my programming habits in the public? Damn most time my left hand moves on its own and all the icons and lines align by themselves just to ease my eyes It does not even take me longer to get my stuff finished. However we LabVIEW programmer are not called 'pixel pusher' for nothing
  6. I absolutely support the considerations of the previous post, so please don't oversize your main VI if it is not absolutely necessary (It never is...). There must be a good reason for programming the SubVIs in the first place. Anyways here is a link to a RCF plugin that should do the trick: Expand SubVI I never used it and I have no advice for installing the RCF.
  7. You might want to read that post to know how to draw attention: http://lavag.org/topic/15044-using-the-report-to-moderator-link/
  8. Well you could. If you write "Arial" instead of "0" than you'll get Arial font instead of the default one. Right now we assume that the default font on an XP machine is different from the one on the Win7 machine. Up till now I couldn't reproduce the behavior on my virtual machine, but I'll try on the real system anyways. I have no access to the target system for some weeks, so feel free to suggest some more ideas
  9. I'll do that for sure. Thanks for the input. The "0"... might be related to an enumeration according to: That would make: 0 = Application Font 1 = System Font 2 = Dialog Font I guess it'll cause the system to use the default LV font that is related to the specific item. I'll try it and tell you guys if it works.
  10. Yeah sorry for that one, I use a translation tool to automatically translate translatable objects on the Runtime system. The source is in English and the target in German. However the controls are the same and the translation has no effect on the positioning. <-- Tested that one already The font is indeed Application Font. Therefore the target system might display stuff a bit different (as with the tab control text width). I'll try that next time I get access to the system.
  11. All controls have the same font. I don't understand how the font type or size should effect the position of the control, but I checked it anyways. On my last post I attached some pictures with an alternative background for the tab-control (the bluish thing...) I accept that the font does have an impact on the position of the text itself (the background seems to small, but actually the text changed its width). What beats me is that if I make a shift-right / shift-left in the dev-environment the Runtime does sometimes look just fine... Is there some kind of raster that I can't see?
  12. I had no access to the machine untill right now. Find the pictures attached. Notice that some items move positions and the blue background-item (or how to name it) is shortened. LabVIEW Environment (Win7 + LV2011) Runtime Environment (XP + LV2011RT)
  13. Hello everybody, I've got a situation where some controls change their position on the build application however only on the target system. This is not just limited to a specific type of control and it does not even effect all controls on the same FP. Up till now the behavior seems to be limited to controls inside a tab-control. My development machine is Win7 with LabVIEW 2011 installation and the target system operates on XP. I'm not to much bothered by it since it does not effect my main UI (which is build using classic controls btw), but it is a rather strange behaviour. Now for a solution: I had some good results by moving the controls in the dev-environment with space-right / space-left once, therefore the position is not altered, but the build application seems to run just fine for most of the controls. I might be able to post a screenshot next week. Does anybody had experienced a similar behavior with such a setup? This issue might be related to that topic: http://lavag.org/topic/16911-prevent-control-resize-when-changing-monitors/ However my controls change their actual position, where the related topic changes height & alignment (of the text inside).
  14. Just figgured that I misunderstood the issue... I'll open a new post!
  15. It's back online!
  16. Refer to http://sine.ni.com/nips/cds/view/p/lang/de/nid/209027 for information about the OpenG toolkit. It includes the VI you are searching for (see jcarmodys post for a picture). An alternative option to this solution is to use the property node of the Enum directly. Configure it to return the Strings[].
  17. The problem is down to line 3425 out of 3743 (only about 20 more feeds to go!) I guess the RSS will be back online for all in approx. 2 Weeks
  18. That is weird, I try to load it in Internet Explorer, Firefox, Thunderbird and even on different machines and systems... I tried to read the page source and everything seems to be there (in Firefox)? *start of further investigation I've been told that there is an error console for Thunderbird, so I checked it and There is an error message complaining about line 1036 (not well-formed)... That is: <description><![CDATA[I'm getting a string formatted like this: Q#b Q#b Q#b Q#b Q#b Q#b Q#b Q#b Q#b Q#b... **Just noticed that the special signes got ereased from my post, but you can check the link below... ***Is it possible that the problem is related to special signes of the good-old lavag site before it changed a while ago (the post is from 2005)? Which is related to the post: That line seems to be fine syntax to me (it's a CDATA section, so why the ****), even though we got some special chars in there. However could anyone please explain why it is not working for me? @Michael: Which application did you use to load the page? I guess right now I've two options:
  19. Hello guys, is it just me or is the RSS for LAVA Forums broken? I didn't receive any feed for the last week and already got worried... Check following link: http://lavag.org/rss/forums/1-lava-forums/ For me it shows up nothing (see picture attached). The other feeds seem to work quite fine, so I'm wondering whats going on...
  20. I've encountered the same behaviour in LabVIEW 2011 and previous, where two projects would lock common libraries (which makes oviously sence). However I would swear that closing both projects and returning to the Getting Startet window will unlock everything (unless some VI is for some reason still running in the background). I didn't use LabVIEW 2012+ up till now, so I can't tell if there have been any changes related. Did you check for a change in the behaviour if you close the projects in a specific order? - open 1, open 2, close 1, close 2 -> Still locked? - open 1, open 2, close 2, close 1 -> Still locked? My guess is that LabVIEW does not update the locked status for common libraries in order to prevent re-checking for all libraries (which is like a reload)...
  21. I recently used the MD-V9900 for a project. Did you already contact Keyence for that information? (They send me all neccessary information within an hour) The documents are not on the internet and Keyence will only provide them on a request. You'll receive a mail with a link to the download information. I could present some information, but that wouldn't help you in any way... (also because my documents are in German) There is much more to it than just sending a string, since you must take care of a specific order when it comes to the digital interface and startup/shutdown... My advice: contact Keyence!
  22. Typedes must be used with great care. It is easy to store entire typedef hierarchies to a single configuration file. Once you change your typedef the data could no longer be loaded from disk (this is true for binary files and sometimes for XML files). Searching for all 'Bundle' functions is munch more painfull than searching for a single VI. This is how I do it: 1) If I need to add an input, I extend the existing VI and give the input a default value and make it optional (if possible) -> No changes to existing code 2) If I need to make changes that are not compatible with the existing version (new connector pane pattern, required input, VI behaviour), I create a copy of the existing VI that must be used from now on (*_V2). The old VI gets a red background and propper documentation (depricated) -> Changes to existing code only if nessecary Notice: I provide the VIs on a seperate palette, so I can guide my collegues in that way.
  23. I tried the XP Mode (Virtual-PC) on Windows 7 for LabVIEW 8.6 once, but the performance is very slow and sometimes a window goes missing. Now I use Virtualbox with acceptable performance. I've seperate environments for LabVIEW down to 6.1. The best choice however is a seperate installation of the required OS on real system to get access to your entire hardware.
  24. You're right. Should have tested it...
  25. Well I guess you could cast your class to a more generic class (within the 'Read Trip' implementation of the child) and then call the parent class implementation of your 'Read Trip' method.
×
×
  • Create New...

Important Information

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