Jump to content


  • Posts

  • Joined

  • Last visited

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since

MartinGreil's Achievements


Newbie (1/14)



  1. Final answer from NI (USA): German: leider gibt es für den Endanwender keine Möglichkeit, die Konturen der Bedienelemente frei zu bedienen. Einzige Lösung ist das Überlagern des Controls mit z.B: Decorations, um die nicht aktiven Flächen zu "verstecken", English: Sorry but there is no way to design custom shaped controls. The only way is to use decorations in front of your control to hide nonwanted active click areas. NI said, i should do it with an AxtiveX Control.
  2. One week and some very long nights later: I have to give up - it seems to be impossible to solve this problem.(also no success with word or powerpoint 2003) I will call the NI-Hotline so see if they have the secret dirty trick. cu soon Martin
  3. Hello, is it possible to create a Boolean control, with a non square outline? (e.g. Jigsaw , PAC-MAN , Star …) I'm thinking about importing a picture which has transparent pixels. The control must only respond on mouse clicks inside the control e.g. not in PAC-MAN's mouth. How did NI create the 'Modern Style' Vertical Toggle Switch? It has the desired behavior. I tried to customize it, but after picture import (*.PNG) the clickable area expands to the full square. Greetings Martin
  4. 1. Create a new toplevel VI 2. on Frontpanel insert 4 SubPanel 3. on Blockdiagram insert a "Static VI Reference" and wire it to the "SubPanel" Invoke Methode. 4. rightklick on "Static VI Reference" => Browse for Path..." and select your VI to view inside the first subpanel. 5. do the same with the other 3 SubPanels 6. close the frontpanels of the 4 subvis 7. during runtime of the new vi you can see the subvis - (you may add a 5 sec delay to the toplevel VI) It looks like 4 holes in the toplevel vi. The subvis are complete independend from the toplevel VI - so you must Run them separately or use them as subvis inside blockdiagram of the toplevel VI. greetings
  5. Sure, a SubVI is a solution - but keep in mind there are hundreds of types possible. The DBL was just used to make an example. So finally your code has to deal with variant data type and set the SubVI to re-entrant enabled. Option "re-entrant enabled" will lead to waste lot of memory when using lot of instances and big arrays. And of course passing data to the SubVI is less efficient than having the data in the local vi. You could improve your VI by passing the Loop's "N" to your SubVI. Then (only in the last iteration) give the array to the output. I don't know if LV can release the allocated memory during the loop of the last call. The LabVIEW generated code would be much more efficient than using a SubVI.
  6. QUOTE (neB @ May 2 2008, 05:56 PM) sorry, I have only LV8.2.1 installed. (I had this idea in december 2006, and found that vi today on my old computer. As far as i know it was sent to NI but never got a reply.)
  7. Compare the upper loop with the lower loop. Take a close look at the loop exit. greetings from martin
  • Create New...

Important Information

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