Jump to content

Recommended Posts

19 hours ago, ThomasGutzler said:

Could you make a package that opens in VIPM 2016? For complicated reasons, I can't update to 2017 :(

Repo is on Bitbucket.  The VIPM build is "Flat Controls.vipb".   See if you can build it under VIPM 2016.  Even if you can/t, you can just take the controls directly from source.

Link to post
Share on other sites
  • 2 years later...

Hi, I made an application in Labview 2013 SP1 using silver controls palette. Then, I replaced with the beautiful controls of Flatline library. Now, my UI looks really nice :). But, when I look up the memory usage of my new “flat” app version, I noted that it increases (near the double) of my originally “no flat” appl memory usage. After a while of running the app, the memory usage is reduced to the original value . Have you noted this extra memory issue? Can be related with the flat library? Should I check an extra option on the app's bulit option? Thank you very much

Link to post
Share on other sites

I have never noticed any memory issue, and I wouldn't expect memory as a potential issue with customized controls (the issue that can affect controls is an excessive redraw rate that shows up as a higher CPU load, not memory).

Link to post
Share on other sites

LabVIEW ctrls DO cause problem sometime.

See my post:

 

It seems LabVIEW has problem with translucent images occasionally.

Even if the image is copied from the Silver Button.

 

Edited by Zou
Link to post
Share on other sites
  • 2 months later...

Note: the latest 1.9.1 version includes an important bug fix: https://bitbucket.org/drjdpowell/flatline-controls-for-labview/issues/5/control-freezes-ui

Because these are controls, previous copies are not automatically updated, and will need to be swapped out.  The affected controls are strings, filepath and combo boxes.

Link to post
Share on other sites
  • 3 weeks later...

I am trying to use these suberb controls in Labview 2019 but I have many troubles.

The boolean buttons have a strange behaviour. When the VI is not running, they are blue (for dark ones) or transparent (for clear ones). Then I run the VI and they remain in the initial color unitl I click them. After the first click the color changes to dark green for True state and grey for False. When the VI stops, they go back to the original color (blue or clear). Even worse, when pressed the first time, the button is no more a rounded rectangle but becomes a normal rectangle. Even the color reported in properties is not correct: for dark (blue) buttons it is blue for False and Black for True, but the button just does not follow this schema when pressed.

Am I doing something wrong?

Link to post
Share on other sites
Posted (edited)

What version are you using?   The latest version in VIPM is 1.9.1.33

Can you post a VI showing the behavior?

Edited by drjdpowell
Link to post
Share on other sites

Hello, thank you for prompt answer.

The version I use is 1.9.1.133.

ButtonTest.png.cac8bf22561caf005aa89945011819de.pngI have now installed the vip library; unitl now I used your controls by extracting them directly from the vip file with 7zip. I usually tend to not install libraries if not really needed.

Now that the library is installed, I had discovered that the buttons that gave me problems are in the OLD palette folder.

Anyway, even if properly installed, the button colors are still not coherent. See the attachment.

I'd also like to use the OLD buttons, since I need the icon.

Thank you

Raf

Link to post
Share on other sites

Why not just use the new buttons, with icons, which you can find in the pallets now that you have installed the package?

These buttons are created from the system button, in order to get hover states.  System buttons don't support the button colours, unfortunately.

Link to post
Share on other sites

Ok, thank you for clarifying this.

Hope one day NI will release a slightly more decent control customize editor. The current one is still a real pain..

Raf

Link to post
Share on other sites
35 minutes ago, Raf73 said:

Hope one day NI will release a slightly more decent control customize editor. The current one is still a real pain..

NI already did: it is called LabVIEW NXG. NI created NXG specifically to address weaknesses in LabVIEW 20xx UI layer. The LabVIEW 20xx editor is antiquated, but its C++ code is very hard to modify. Given that NI's focus for user interfaces is almost entirely in NXG, there is very slim chance of further developments ever in the LabVIEW 20xx control editor. I cannot say "no, never" just as I never promise "yes" on future functionality even when I'm actively working on it, but I will say that it would take significant user encouragement for NI to fund the 20xx control editor ahead of other 20xx priorities, and I don't expect that to happen.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By drjdpowell
      A set of custom controls, following the trend of a more flat UI design.  Heavily influenced by Google’s Material Design, though constrained by what can be done with available tools and options in LabVIEW.  Uses icons from Google Material Design.
      — Buttons based on the system booleans (with hover effects).  Icons can be added as decals (such as from materialdesignicons.com) 
      — Matched sets of controls for numeric/string/enum/etc., based on Silver controls, but swapping out all ‘chrome’ for simple boxes and lines.
      — flattened versions of switches/sliders/arrays/graphs etc.
      Now on the LabVIEW Tools Network
      JDP Science Tools group on NI.com.
    • By drjdpowell
      I’ve been trying to come up with my own consistent set of custom controls that has a more modern “flat” or “near-flat” style.  Largely this was inspired by reading Google Material Design, and I’ve just added the results as a package in the CR: Flatline Controls.  The latest thing I’ve been toying with are slider switches (here the Material Design guide on switches).  But I’m having a hard time coming up with something that is flat and non-skeumorphic, but also clearly a switch.  Attached is a VI (2011) with multiple switch types.  The most 3D, old-school, looks like a real-world switch (on the left) seems best in terms of being obviously a switch.  My most Google-like switch, on the right, is flat and simple, but not immediately obvious.

      My question is: what of the multiple LabVIEW switches do people actually use? 
      Trouble with Switches.vi
       
    • By MarkBarnes
      Hi all,
       
      I'm trying to anti-alias my vector-based custom controls. I know it's possible:
       

       
      The left hand circle is my custom control, the other 3 are various circular controls taken from the Silver controls palette.
       
      Obviously the anti-aliasing is not a public feature and is part of NI's internal control definition. Has anyone succeeding in either exposing this hidden property as something to be turned on, or editing the raw .ctl file code to enable anti-aliasing? 
       
      Any ideas?
       
      Thanks,
      Mark
×
×
  • Create New...

Important Information

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