Ton Plomp

QUOTE (Norm Kirchner @ Jun 30 2008, 03:19 PM) Here Here. Ton

QUOTE (MaRine @ Jun 30 2008, 08:48 AM) What is exactly the problem? The (always) changing date is that part of the enum string? If so, don't do this! I think you should try to print a label from a simple VI, and then place it into your state machine. Ton

QUOTE (Yair @ Jun 29 2008, 08:19 PM) No need to make it non-reentrant, LabVIEW 8.5 can debug and probe reentrant VIs. Ton PS Jeff Washington thanks for that feature

Just because there's a kid inside us all.... This Gizmodo post made me allmost cry. Ton

QUOTE (labc @ Jun 26 2008, 05:50 PM) Dropping directly from another program can be done by creating an invisible path control. A little example is given on the http://digital.ni.com/public.nsf/allkb/81D867F8C6A1376D86257347001BE936' target="_blank">NI KB. Ton

QUOTE (Etienne @ Jun 26 2008, 05:44 AM) Hi etienne, You could use the http://forums.lavag.org/Boolean-XControl-file104.html' target="_blank">Boolean XControl to have buttons with configurable icons Ton

Don't use the 'stop function' QUOTE (Thang Nguyen @ Jun 25 2008, 09:05 PM) Your while loop waits for the 'Create ActiveX Ref VI', so the abort will not happen. Is that the same VI you openend dynamically? If so try the following structure: http://lavag.org/old_files/monthly_06_2008/post-2399-1214422483.png' target="_blank"> Ton

QUOTE (Jim Kring @ Jun 24 2008, 11:16 PM) Yes I know that one, is quite cool. But the http://wiki.lavag.org/Code' Capture Tool' rel='nofollow' title='LabVIEW Wiki article on Code Capture Tool' alt='Wiki article on Code Capture Tool' style="border-bottom: 1px dotted #3366BB; color: #3366BB; cursor:pointer; text-decoration:none;" class="wiki">Code Capture Tool isn't helped by this solution. Ton

QUOTE (nhollenback @ Jun 24 2008, 09:57 PM) You know there are just 16 colours, right? The 32^22^32-16 are just marketing mumbo jumbo? Ton

Has anyone else seen the following issue on Firefox 3 (here as well on the dark side)? If I click inside the attachments string field a browse dialog pops-up. I don't want that! There is a separate browse button next to it. EDIT: And we have a mozilla thread Ton

So you are all transtitioning to a platform that isn't backwards compatible? (OS flame war awaiting) And you really want to wear blue shoes? Ton

QUOTE (JDave @ Jun 24 2008, 08:38 PM) I don't think an event is fired if the same value is selected again (haven't tested). Ton

QUOTE (JDave @ Jun 24 2008, 08:14 PM) I am currently working in 8.2 and they are not present there, but they are available in 8.5 (they seem to be private though): I assume they are private because the help goes nowhere. Eugen, Is named Numeric size the one you are looking for? Ton

QUOTE (neB @ Jun 24 2008, 06:33 PM) As soon as you hover the options you will get a mouse-leave event. This can be triggered by just clicking the control. But hey a ring control has two super-duper events: 'Activated' this one gets triggered as soon as the control is clicked 'Dismissed' if the Activated event is well ehm dismissed Ton

There's a property that returns an array with all the monitor sizes: Ton

XControl storage comes in two parts, saving and retrieving: Saving is done with the XControl:Abilities:Convert_state_for_save_Ability_VI. Retrieving is done with the XControl:Abilities:Init_Ability_VI. To trigger the convert state for save ability you should save the owning VI, this VI has a variant container for the data of the XControl. In the Init ability you can read back this variant. Inside your State ability you could have two sets of data, Current with the settings currently used, and Default with the default parameters, inside your XControl you could write code that copies Current to Default and in the convert state for save ability you only store the Default parameters. Ton

QUOTE (David Leeee @ Jun 24 2008, 05:47 AM) Yep, here's the http://zone.ni.com/reference/en-XX/help/371361D-01/glang/set_menu_item_info/' target="_blank">help. When the enabled input is set to 'F' the item will be grayed out. Ton

QUOTE (Aristos Queue @ Jun 16 2008, 03:43 PM) The other points make sense, this one a little bit less. LabVIEW is an IDE, so it makes sense to write tools that make the life of LabVIEW programmers easier. This is IMHO not an NI exclusive field of products. Some of the private options and methods are so valuable that opening them will be very very nice. There are quite some properties that aren't available in the Runtime Engine so why not just a little bit more? Ton

QUOTE (Antoine @ Jun 19 2008, 11:59 AM) What's wrong with Hardware Ton

Also participating in the 'how many times do you have to refresh your webbrowser to load the page' contest. Ton

QUOTE (Götz Becker @ Jun 16 2008, 03:53 PM) One question is the U8 converted or typecasted? With a typecast the U8 is placed in the upper byte of the U16. Ton

QUOTE (normandinf @ Jun 13 2008, 02:08 PM) I wonder why these items are password-protected? I can see no reason, to make these methods only available to LabVIEW R&D. Could someone of NI clarify this? On a usability note: I think this method should be a read-only property. Ton

Is there a reason why I can't tag twice the same tag (on different messages in different threads?) I couldn't add the tag 'Private Method' to this post. Ton

There is a private method returning the most recent used files and projects (seperatly): Ton

QUOTE (GregSands @ Jun 13 2008, 05:57 AM) 1: Never, ever do such a thing. If you as much as repair LabVIEW you will lose your changes. 2: The safest solution, but if NI finds a bug in one of the VIs it is very hard for you to trace. 3: That would be my option I would keep as much VIs in the same place. So only move the VIs (and it's parents) to a development place. User.lib is not a place where you keep VIs in development. Give the description of each VI a common tag like <ChangeForEnhancement> followed by the name and location of the original VI. Personally I have my tools under SCC in a different location, I built a toolkit of it and that toolkit gets copied to user.lib Ton