[CR] Flatline Controls

[drjdpowell]

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.

[FlaviaF]

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

[drjdpowell]

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).

[Zou]

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 February 20, 2020 by Zou

[drjdpowell]

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.

[Raf73]

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?

[drjdpowell]

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

Can you post a VI showing the behavior?

Edited May 19, 2020 by drjdpowell

[Raf73]

Hello, thank you for prompt answer.

The version I use is 1.9.1.133.

I 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

[drjdpowell]

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.

[Raf73]

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

[Aristos Queue]

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.

[drjdpowell]

I didn't think NXG had a control editor yet.