JDave

Thanks for the ideas. The NICs are on different subnets, but I was not aware of that usage of StringToIP. Oddly the function shows both NICs even though the TCP Open does not correctly connect. I don't know whether it has anything to do with the XP Embedded, but I am going to just use a launcher executable. I have already spent way too long on this and I just can't make sense of why it is acting strange.

I am having some problems with a LabVIEW application of mine. It is set to auto-run on startup, and the OS is Windows XP Embedded. I am trying to add a NIC to the system to allow for Ethernet communication. That makes two network interfaces, since there is one built-in network interface that is being used for control of some internal RF ComBlocks. The problem I am seeing is when I attempt to open the connection to the ComBlocks I get an error because the correct connection is not made. Disabling the second NIC solves the problem, but even trying to hard-route a connection using ROUTE ADD doesn't. The only thing that has worked has been to have a launcher executable run at startup instead, and then after some delay launch the real program. However, if I put the same delay within and at the beginning of the 'real program', it fails. This all seems to indicate that the OS has not properly initialized the Ethernet connections at the time my application runs. I am almost resigned to just having a launcher executable, but I wanted to check and see if there was some way of querying the active interfaces available. Or if there was some way to force TCP Open to choose the correct interface that would be nice too. Ideas?

Name: Array Point to RowCol Submitter: LAVA 1.0 Content Submitted: 03 Jul 2009 Category: General LabVIEW Version: 8.0 Version: 1.0.0 License Type: GNU Public Potentially make this available on the VI Package Network?: Undecided Copyright © 2006, dsaunders All rights reserved. Author: dsaunders --see readme file for contact information Description: Converts a pixel coordinate to an array index. Returns an array of indices with a length equal to the number of array dimensions. Also returns if the point is within the content rectangle (not on the caption, scrollbars, etc.) Works on any N-dimensional array regardless of visibility of caption, label, index display, or scrollbars. Designed to be used on mouse events that provide the mouse coordinates. Limitations: Property nodes do not indicate the array border width, nor if the user has chosen to display an element gap. These inputs are thus provided on the VI. Version History: 1.0.0: Initial release of the code. Click here to download this file

Name: Type Sensitive Popup Submitter: LAVA 1.0 Content Submitted: 02 Jul 2009 File Updated: 04 Jul 2009 Category: User Interface LabVIEW Version: 8.2 Version: 1.0.1 License Type: BSD (Most common) Potentially make this available on the VI Package Network?: Undecided Copyright © 2007, David Saunders All rights reserved. Author: David Saunders --see readme file for contact information. Description: Provides an intuitive interface for tabular controls containing multiple data types. Users can use various controls and datatypes. Users can also use provided functions for registering and looking up type parameters by control (as well as by column, row, or cell). When you click on a cell, a correctly positioned and sized popup appears allowing for a controlled and intuitive input. Appears like it is a built-in feature, not an annoying popup window. Features: - Supports tables, listboxes, multicolumn listboxes, trees, and string controls. - Implements many data types : string, integer, float, color, ring, boolean, captioned string, etc. - Can use multiple tabular controls in same program with no programming changes - Can pre-register controls with certain data types - Register the entire control, or columns, rows, and cells. - Can edit the registered data type by registering again at any time - Allows for different font sizes - Works even on modal windows Instructions: Run the Demo program to see example usage. To recreate -- 1. Drop 'TSPopup.Popup Cluster.ctl' anywhere on your front panel. 2. Create program logic, similar to the demo MANDATORY elements a. TSPopup.Initialize.vi (register for the user event in your event structure) b. TSPopup.Lookup.vi (returns positioning information, looks up any registered controls) c. TSPopup.Show Popup.vi (called in a Mouse Down? event case) d. an event case for the user event output from (a.) e. TSPopup.Close.vi (called at end of program) OPTIONAL elements f. TSPopup.Register.vi (register controls with popup type parameters) g. TSPopup.Update Cell String.vi (provided to show how to change the cell string after popup is completed) 3. Bring the Popup Cluster to the front on the front panel. Otherwise the popup will show up behind some of the other controls on your User Interface. Limitations: - Can't programmatically bring popup cluster to front. Must do this manually. Change Log: 1.0.0: Initial release of the code. 1.0.1: Added another demo using dynamically changing data types in a tree Removed LV version specific event handling (only dealt with LV 7.1) Fixed bug where headers defaulted to have same type as their column/row Fixed cluster scanning from text Fixed ring to default to index 0 if string unrecognized Changed the background event monitor to always be hidden Click here to download this file

It's comforting, after being away for quite a while, to be scanning the recent threads and see this one. Thanks, alfa.

QUOTE (Jim Kring @ May 27 2009, 10:30 AM) It was really cool to see something I started show up in your video! I am really glad that you were able to finalize it and figure out the scripting magic that I never did figure out. I would love to see what was done; I look forward to that!!Great job with the Framework! It is a great extension to the LabVIEW IDE and to the concept started with VIPM. Keep the awesomeness coming. David

QUOTE (alfa @ Sep 4 2008, 12:05 AM) It certainly matters where you are (and I am SO interested in finding out what percentile you fall into...). If you came up with the idea the only 1 in 1300 people are fully awake, did you manage to do that while not being fully awake? Aren't you inherently including with this theory that you are one of the blessed few? If you are then congratulations are in order. But as Rolf already pointed out, your ideas don't exactly encourage people to congratulate you. Though if about 1300 people read this thread, then you may help the enlightenment of a blessed soul.

QUOTE (Aristos Queue @ Aug 30 2008, 01:27 PM) I don't use libraries so I'm a bit confused by this. If I understand correctly, and if the feature of overlaying the access scope on the icon were developed, C.vi is would show up as public if dropped on a vi within B.lvlib. C.vi would show up as private if dropped on a vi withing A.lvlib. And C.vi would break a vi (possibly different overlay) if placed elsewhere. Is this correct? And that is the issue, that the access scope actually changes based on where it is called? David

QUOTE (crelf @ Aug 29 2008, 09:30 AM) The Icon Editor I created allows for placing images in the corners. It wouldn't be that hard to automatically place the proper image in the desired corner. However, this would probably require knowing the VI ref so you could query. (I haven't looked into this, so I am not sure that it is available for querying...) This is just another reason why it would be nice to know what VI the Icon Editor is manipulating. My current method for getting the VI ref works pretty well, but doesn't handle calling the Icon Editor from an Invoke Node. I use a background process monitoring for the rusty nail VI Activation event.

QUOTE (mballa @ Aug 27 2008, 06:29 AM) I agree that the scripting event is the best that is known out here in the wild. But it doesn't handle situations where it is called through an Invoke Node or from the palette editing area. ThSa even had a comment in his code that handling the Invoke Node was something he hadn't cracked. QUOTE (mballa @ Aug 27 2008, 06:29 AM) I would agree with PJM on this one, If you want to do several different things to a VI : Fix the FP, Set Description, Hide/Show toolbars, and Icon editing then you start with a Main that is designed to do this. Taking an Icon editor and changing it into a vi editor is not the best way to approach this. My current Icon Editor does not do this and I agree that cluttering the interface is not desired, but someone had mentioned that they liked this functionality. I can appreciate the convenience of having the two together if it is not intrusive (perhaps a menu option). However, I also like to have the filename of the VI so that I can parse it and auto-generate some text for the icon. It's nice to only have to name the VI once.

I was hoping to get some discussion on the points I brought up ... But if nothing else, What I really want is to know if there is some way to know definitively WHO the icon editor is 'editing'. This would be necessary for allowing things like editing the description. Can someone from NI point us in the right direction here? Is it at least something under consideration for future versions of LabVIEW?

Regarding 3-Button Dialog: I must say that the issue of performance is somewhat out of place when it is specifically stated that the 3-Button Dialog is a UI. Performance is really important for the work code that crunches in the background. But I have always heard that when it comes to user interfaces, maintainability and speed of programming is always more important than speed of execution. Is the user really going to notice the extra 20 milliseconds? David

QUOTE (LV_FPGA_SE @ Aug 20 2008, 06:25 PM) Good answers!! I would hire you if I could. This being that you also pass the test of having many good posts here on LAVA.

QUOTE (crelf @ Aug 14 2008, 05:41 PM) How silly of me. I think you have that backwards. When you install a custom icon editor (place a lv_icon.vi file in the plugins directory) it always shows up when editing an icon. You can cancel out of it in such a way that you revert temporarily to the standard LV icon editor, but you can't go back the other way.

I drew up a quick Front Panel to allow some discussion here. It includes the standard look, plus a tab control on the right for various options. I included a toolbar area on the top for quick access to changing the header and body and frame colors/images. The first box would house any selected image, and the black-on-white boxes would be the FG/BG colors. The dropdown on the top right would be for selection of saved themes/configurations.

QUOTE (PJM_labview @ Aug 12 2008, 03:12 PM) Does this happen when all the colors in the 256 color icon correspond to white? This could be circumvented by forcing the B&W icon to have a black border if it would otherwise be pure white. In the end, the 256 color icon is the main icon that people will see, and it should roughly define what the other color icons look like. Independently editing the other color options (from what I've heard and seen) is only done because NI forces us to in order to have smaller sized icons. If we could properly convert the 256 icon to the other two formats (including fixing the bug that Ton mentioned) then I think we would be much better off. Having three different icons to edit is confusing to most LabVIEW programmers. QUOTE (hfettig @ Aug 12 2008, 05:56 PM) I am with Philippe on the suggestion that we should include all the functionality of the basic editor. I assume that the original icon editor is protected so that we could not simply add to it? Without integration of the original features I do not see a large number of users adopting a different editor simply because they are too used to it. This does require some juggling between mouse-drawn objects and auto-drawn objects. ThSa's only allows one at a time, and if you apply the auto-drawing then your mouse-drawn items disappear. Not saying this is bad or wrong, but it is something to be dealt with. QUOTE (hfettig @ Aug 12 2008, 05:56 PM) I also like ThSa's 4th tab that allows you to set the description of the VI. This is a VERY interesting item. To edit the description, you need to know which VI you are editing. This is NOT KNOWN by any property or method available. I really wanted to see how ThSa was attempting it, but it is password protected. In the end, NI really needs to provide this information. David

QUOTE (PJM_labview @ Aug 12 2008, 12:07 PM) I will post an image with descriptions on those buttons. What would be the use cases for editing each one independently? If you had a document on those NI functions, that would be great ! It would probably be worthwhile to amass a list of desired functionalities (like copying from the clipboard). The solution currently for my implementation is to save that image to the correct image folder and then it would show up in the image search. Though I had considered adding a functionality for importing an image into my 'library'. It wouldn't be hard to extend that to include importing the image currently in the clipboard. I definitely agree that if the user has an image in the clipboard, they should be able to paste that onto the icon somehow. Ctrl-v should work. QUOTE (Michael_Aivaliotis @ Aug 12 2008, 12:22 PM) I hate making icons! I only use text on my icons. I would like to be able to type some text and it gets translated to tiny fonts and auto-fit into multiple lines. Can someone add this? Also, I think it would be awesome to combine all the features into one super LAVA icon editor. Super in functionality however simple and intuitive to use. There is the challenge. Adding features is easy, making them obvious and intuitive is the tough part. I configured my editor to translate/parse the filename to tiny fonts and auto-fit into multiple lines. That way I only have to name the VI once. I don't know if that is quite what you are asking for. Are you thinking more of a single string control to type into?

QUOTE (Antoine Châlons @ Aug 11 2008, 11:22 PM) I agree -- if I know the lyrics it tends to distract me. I like classical or else a totally eclectic mix of songs from my music library ranging all over but successfully skirting around a few genres like Country, Rap, and R&B. Most anything else is fair game... I even noticed that "C is for Cookie" somehow slipped into that mix. http://lavag.org/old_files/monthly_08_2008/post-1519-1218563271.jpg' target="_blank">

Michael, I just wanted to thank you for working on improving the MC Listbox. I loved what I saw at NI Week at your presentation. I have tried to do something similar with making an XControl for the multiple type MC Listbox that I made. I even started playing with making the column resizing work the way you were showing. I didn't get very far, so I was very impressed with what you showed. I was wondering if you purposefully didn't talk about the glyphs in the far left column ... :ninja: Have you considered supporting booleans, rings, etc. in the listbox? The glyphs would be wonderful for implementing boolean selections. I know this is a whole can of worms by itself (assigning data types to columns, handling inputs ) Anyway, great presentation. Glad that I showed up 30 minutes early so that I could actually get a seat.

QUOTE (mballa @ Aug 12 2008, 06:46 AM) I posted an Icon Editor that plays with both text and graphics. It is quite well developed, but tuned to my liking... I really like the idea of coming up with the LAVA Icon Editor. That would be very cool. I would love to help out with that!! Regarding PJM's comment, I had not really considered (ever) mimicking the NI Icon Editor functionality because I wanted to avoid completely all that pixel manipulation when I create my icons. However, I can understand his point that to be widely accepted it has to at least feel comfortable at first glance and while using it. Philippe, were you envisioning keeping the ability to individually edit each of the three icons (B&W,16,256) ? Would there be any problem with just applying the 256 Color icon to the other two?

QUOTE (sachsm @ Aug 7 2008, 04:56 PM) When I have needed this, I just convert to string before passing to subVI. You can make a smaller-sized subVI wrapper around the Scan From String if you need to conserve block diagram real estate. I made a request for exactly this a while back, but I have come to agree with Aristos. I just would prefer a smaller sized icon, similar to those for converting between numeric types.

I looked at the upgrade notes, and not having done any beta testing I was quite happy to see a few upgrades that will be nice for me. Updating properties of multiple items at once (though this wasn't too much of a surprise, given various hints) Quick Drop for keyboard shortcuts to palette items (look familiar, Yair?) and the Tunnel Wiring Wizard ! built into LabVIEW

QUOTE (iowa @ Jul 31 2008, 03:22 PM) Is there some reason you have to do all the Windows API work yourself? I thought the suggestion of using compiled AutoIt scripts was quite nice. AutoIt does all the API work and you just run the exe from your VI. Is there a reason this doesn't work for you?