Ton Plomp

QUOTE(DaveKielpinski @ Oct 11 2007, 11:26 AM) You kill the event registration refnum as soon as the exec change is changed to false (what happens if you load the XControl into a non-running VI. I think my method is the best..... If you want to correct me, please do Ton

QUOTE(DaveKielpinski @ Oct 11 2007, 11:13 AM) You should use a propery 'Value Signalling' Node. A local (or a 'Value' property) won't fire an event. Ton

QUOTE(DaveKielpinski @ Oct 11 2007, 10:32 AM) You can use the Init ability, only make sure you use a dummy registration (as I showed in my Nugget and NI in their example) in the Init. If there's the need for the event registration write the correct control reference to the event registration (if I'm right that's exactly what I did in the Boolean XControl). Ton

QUOTE(Michael_Aivaliotis @ Oct 10 2007, 07:46 PM) In the http://forums.lavag.org/downloads-file104.html' target="_blank">Boolean XControl I do it with the Init and Uninit abilities. Ton

QUOTE(tcplomp @ Oct 10 2007, 07:33 AM) QUOTE(Michael_Aivaliotis @ Oct 10 2007, 08:00 AM) Yes, remove it but how? I meant to say disconnect... It might be like the bundle/unbundle by name where you can only remove an element when it's fully disconnected. Ton

QUOTE(Michael_Aivaliotis @ Oct 10 2007, 02:15 AM) I can't follow the dicussion but maybe this is the solution: http://lavag.org/old_files/monthly_10_2007/post-2399-1191994384.png' target="_blank"> So remove everything beloning to that item. Never tried it but hey Ton

QUOTE(torekp @ Oct 9 2007, 01:40 PM) I'm no expert but as far as I know a VI with only primitives (like yours) can easily be set reentrant since there aren't subVIs that are loaded into memory. Ton

QUOTE(Jim Kring @ Mar 3 2007, 09:00 PM) QUOTE(nicolasB @ Oct 9 2007, 01:48 PM) this looks very interesting but I tried to make this run under LV 8.5 and LV8.2.1 and it doesn't work. Even the "OS Open Document"-Event isn't available in these versions. I haven't tested it in 8.2 but I wouldn't think it has changed. (you can see it probably in VIPM but Michael should know that) Ton

QUOTE(Michael_Aivaliotis @ Sep 26 2006, 09:46 AM) And one place to make these setting! Currently NI always uses the name when app builder was installed! Our company changed names and it seems a little unprofessional if you find the old name in the installer setting under © Ton

QUOTE(Jim Kring @ Oct 6 2007, 01:49 PM) Well it was a long shot, but unfortunately it didn't work. The localized name is accessed via the 'Properties' 'Documentation' it is present because NI wants to use for every language version of LabVIEW the same lvclass file. Ton

QUOTE(Jim Kring @ Oct 5 2007, 10:42 PM) Have you tried changing the localized name? Ton

QUOTE(Michael_Aivaliotis @ Oct 4 2007, 09:07 PM) Easy, take your time Ton

I think in the last update the add wiki tag option is removed from the posting page. Under Quick access there was a possibility to add a link to a wiki file. Is this done on purpose or am I looking at the wrong place? I love the WIKI and was dissapointed when the wikifier was removed due to bugs Ton

QUOTE(Jim Kring @ Oct 4 2007, 06:07 PM) QUOTE(gmart @ Oct 4 2007, 07:14 PM) I should have been more clear. The File I/O functions (primitives) don't work with LLBs. Some of the File I/O VIs do. And I should have said project libraries and their variants (lvclass, etc.). Thanks for cleaning up my mess, Jim :thumbup: Why is everyone always forgetting XControls? :question: Ton

Too bad you didn't post some code you allready tried, now we have to guess. I would try this: Ton

QUOTE(dannyt @ Oct 1 2007, 05:58 PM) Well the issue is lvproj don't cover dependencies (which are the case here). What you need is some form of database. Every VI call should there be logged, but you will always miss dynamic calls. So the problem is not the owning VI, but the subVI. If you need to change functionality of a (very often used) subVI, you need to recreate it under another name. http://wiki.openg.org/Library_VI_Deprecation_Process' target="_blank">OpenG has some policy for this Ton

I hope it works as good as you think since you are resizing the array all data after the 'UsedInTestSequenceID' Array has to be shifted I think the inplaceness is superb for inplace items where you don't resize items. Ton

QUOTE(NormKirchner @ Sep 26 2007, 10:17 PM) I'm not sure what you want but maybe the 'track' option on the upper right hand corner is a good start? http://lavag.org/old_files/monthly_09_2007/post-2399-1190872203.png' target="_blank"> Ton

QUOTE(Bingo @ Sep 24 2007, 05:52 AM) Hi Jack, what I would do is use some messaging, the init state triggers the 'Display State Change' event int the facade VI. The init VI should only be used to load the previous run information and allocate some resources. What is it that you whish to do? Ton

Thanks PJM, but this is the link should be: Ton

QUOTE(jdebuhr @ Sep 20 2007, 06:45 PM) The 'Mouse Down?' is a filter event, it allows you to cancel the event so it is fired before the 'Mouse Down' event. It can be usefull if you don't want to change the value of a boolean after a mouse click in certain conditions. But I wouldn't use the 'time-out' option because 5 seconds is a long time, and you have most likely other events in the same structure. I would start a fire a second loop that waits for 5 seconds on a notifier, if the notifier is not fired the numeric will be reset. You fire the notifire on a 'mouse up' Ton

QUOTE(Ben @ Sep 20 2007, 12:52 PM) Yep: http://lavag.org/old_files/monthly_09_2007/post-2399-1190285881.png' target="_blank"> Ton

I have just finished read Joel Spolsky post on his blog. It's about history repeating in software world and the future of web-apps. And I couldn't help myself thinking about LabVIEW (who cares the runtim is 100 Meg, I don't) It's every minute worth reading (like a lot of his posts), he knows why the Microsoft has a 29 february for 1900 (no it's not a fault of MS). It's kinda fun to read his posts Ton

QUOTE(Jeffrey Habets @ Sep 19 2007, 02:03 PM) I've been thinking a little about this, what you expect is a read-only 'value' property for latches and a read/write for switches. But there's an issue. Value is a property of the 'Control' class... and not of a '...... Control'. So the Boolean latch class should disable the write property of a Control. And using a the 'dynamic casting' as you showed force me to use two event cases with the same contents. Ton

QUOTE(Jeffrey Habets @ Sep 19 2007, 09:41 AM) Yes I know that, but it should not matter, the data-type should be boolean wheter it's a latch or switch (right?) A latch should fire an error if the wrong boolean type is used. I propose two have two boolean reference types: Switch Latch Ton