PJM_labview

QUOTE (normandinf @ Jan 16 2009, 07:32 PM) I see that you use the input VIs to solve this issue. Unfortunately, I need a cross platform solution and the input VIs do not exist on Mac. Note: If I can not find another solution, I will use this. QUOTE (Darren @ Jan 16 2009, 09:10 PM) In LabVIEW 8.6 there is a private event called "Shortcut Menu Dismissed". There's also the equally-handy "Operate Menu Dismissed" that fires when you dismiss the operate menu of a ring, enum, etc. -D This is good to know. Now I just have to figure out how to do that in LV 8.2... I found a way to get at the "click outside of LV" info. I create an asynchronous VI with both attributes of "floating" and "hide when LV not active" set to true. When this VI "FP.State" becomes "hidden" I fire a user event that tells me that LV has becomes "inactive". Now I am left with trying to find out whe the user escape out (press ESC) of the Run-time Shortcut Menu.

Workaround: Have a grid (with snap to grid enabled) on the BD. This makes doing this pretty easy (not as easy as having a button though). Note: Ctrl+Shit+3 disable the snap to grid (oddly enough it is persistent for all VIs as this settings is saved in the LabVIEW.ini)

Workaround: Have a grid (with snap to grid enabled) on the BD. This makes doing this pretty easy (not as easy as having a button though). Note: Ctrl+Shit+3 disable the snap to grid (oddly enough it is persistent for all VIs as this settings is saved in the LabVIEW.ini)

Hi, I am trying to find out if there is any way to know when a user discard a Run-time Shortcut Menu (in LV 8.2, 8.5 or 8.6). For instance I am trying to find out when the user either: Press ESC when the Run-time Shortcut Menu is visible Click outside (of any LabVIEW window) to "escape" the Run-time Shortcut Menu As far as I can tell there is no way to get this information. Thanks PJM

Hi, I am trying to find out if there is any way to know when a user discard a Run-time Shortcut Menu (in LV 8.2, 8.5 or 8.6). For instance I am trying to find out when the user either: Press ESC when the Run-time Shortcut Menu is visible Click outside (of any LabVIEW window) to "escape" the Run-time Shortcut Menu As far as I can tell there is no way to get this information. Thanks PJM

QUOTE (george seifert @ Jan 14 2009, 01:09 PM) Yes, you could do that. This is just an implementation choice. I also like to use custom glyph as much as possible and I try to tie the tree/listbox glyph to the visible tab/subpanel (see VIPM screenshot below). This give visual cues to the user and it makes operating these UIs easier. http://lavag.org/old_files/monthly_01_2009/post-121-1231968862.png' target="_blank"> PJM

QUOTE (george seifert @ Jan 14 2009, 01:09 PM) Yes, you could do that. This is just an implementation choice. I also like to use custom glyph as much as possible and I try to tie the tree/listbox glyph to the visible tab/subpanel (see VIPM screenshot below). This give visual cues to the user and it makes operating these UIs easier. http://lavag.org/old_files/monthly_01_2009/post-121-1231968862.png' target="_blank"> PJM

QUOTE (george seifert @ Jan 14 2009, 11:10 AM) It is hard to give you a silver bullet that cover all the use cases. Basically it depend of what type of data you are trying to display and what type of feedback you expect from the user. My rule of thumb is that if I get to a multiline tab control I should figure out another way of displaying this info to the user. One approach is the LV Option Window (or the LV build spec window). I agree with CRelf that this is essentially a tab control, but it does not look and feel like a tab control. Also, every time you can guide your user (instead of displaying multiple row of settings in a tab control) the better it is (see CRelf screenshot above where he has navigation buttons [next back...]).

QUOTE (george seifert @ Jan 14 2009, 11:10 AM) It is hard to give you a silver bullet that cover all the use cases. Basically it depend of what type of data you are trying to display and what type of feedback you expect from the user. My rule of thumb is that if I get to a multiline tab control I should figure out another way of displaying this info to the user. One approach is the LV Option Window (or the LV build spec window). I agree with CRelf that this is essentially a tab control, but it does not look and feel like a tab control. Also, every time you can guide your user (instead of displaying multiple row of settings in a tab control) the better it is (see CRelf screenshot above where he has navigation buttons [next back...]).

QUOTE (jdunham @ Jan 14 2009, 08:38 AM) I agree. I think they are the front panel equivalent of the sequence structure... PJM

QUOTE (jdunham @ Jan 14 2009, 08:38 AM) I agree. I think they are the front panel equivalent of the sequence structure... PJM

Maybe this post will help (it is about linux, but you never know...). PJM

QUOTE (Ton @ Dec 23 2008, 09:01 AM) Ton, This is what the description field of the package says: "Version 2.2 adds support for appending files to an existing archive, deleting files from an archive and password support for adding and extracting files. Version 2.3 adds support for transparent Mac Resource file handling through MacBinary encoding. Version 2.4 adds support for direct memory stream handling." PJM

I think the misunderstanding might not be with us. The method I described earlier works regardless how many transparent area there are in the image. Below is another short video using a more complex (transparency wise) image. PJM

Interesting Trick Norm! Thanks for sharing. PJM

QUOTE (Yair @ Dec 20 2008, 08:27 AM) Nope. Still works fine for me (see below). Note: Watch the little gradient block as I move it in the image. PJM

QUOTE (asbo @ Dec 19 2008, 07:01 AM) This was my initial though, but I don't see why doing a "save as>>copy>>create unopened disk copy" would do such a thing. May be this has something to do with a VI in the clipboard... PJM

QUOTE (Cool-LV @ Dec 18 2008, 04:24 PM) I am sorry, but I can't share this code. Here is more info that should help. As other have mentioned, after reading a PNG file the image data cluster does has the alpha blending info in the image array as [ARGB] (Alpha Red Green Blue). Once you got the image data of the pixels directly "behind" you new image, you could now recompute each new pixel color with: ResultingColor = SourceColor × alpha / 255 + BackgroundColor × (255 - alpha) / 255 Note: You need to operate on color plane not on LV color. I hope this help. PJM

QUOTE (Ton @ Dec 16 2008, 11:04 PM) Ton, is correct. I have code that I wrote a while ago that do just that and it works like a charm. PJM

After doing a "save as>>copy>>create unopened disk copy" I got the following error messages. I am not entirely clear about the meaning of this message. PJM

I can see this as being useful if you do not have a palette for all your wrapper members. If you do have a palette, LV give you very quick access to all the member of the same palette (see screenshot) and I do not see any advantage to wrap everything in a polymorphic VI (neither do I see any inconvenient to have a palette with a "lot" of items). Additionally, in my opinion, maintaining polymorphic VI is a pain (this is a cumbersome process). So, I will add another con: Maintaining polymorphic VI is a pain.

They are good! :thumbup:

What you want to do is pre-load your images prior to really communicating with simulink (see screenshot). Attached is the code that do this. Download File:post-121-1228502405.zipLV 7.1 Enjoy PJM

QUOTE (Cool-LV @ Dec 2 2008, 10:41 PM) http://forums.lavag.org/VI-Scripting-Readme-First-t1207.html

QUOTE (Darren @ Nov 21 2008, 11:02 AM) Not if the item you replace is a merge VI Dynamically, create a new VI (in memory) where you can can use scripting to drop a VI from disk (using the New VI Object function you mentioned earlier). Now save this VI as the merge VI replacement and the drop will work fine (with no linking issue). I typically use the true constant merge VI to do this. PJM