Jump to content

Lipko

Members
  • Posts

    73
  • Joined

  • Last visited

Everything posted by Lipko

  1. Graphs + plotimages of graphs also has pretty good contomization potential. Horizontal fill: A failed project with some flat controls, all my design, though I don't quite like it, I'm not good at visual design. Note, that it's meant to be a tablet application, but it has no exit button The room is a 2D picture and slots can be selected by clicking.
  2. I use splitters all the time, but making a tab control responsive, I failed miserably with that. Positioning and grouping of widgets on one page screws widgets on another one... Especially if there are graphs which are clumps of widgets by themselves. A test sequence editor (this has no problems with responsivity) which has a ribbon bar and some other splitters. The comment of some selected sectios are being edited at the moment (double click on the time line invokes a positioned text control)
  3. Yes, I was thinking about something like those! I'm thinking about what I could share, but most of my GUIs fail or may be confidential to show.
  4. That's true but by good looking I don't only mean the actual looks of the widgets (for example the silver theme looks good enough for me. Or there are some 1px border cluster hacks that someone already did so you don't have to do it yourself and greatly improves the look), but the way the widgets are arranged, grouped, or hidden. Even for an industrial HMI, most of the time you just need to load some test sequence, some parameters from a file that (hopefully) doesn't change without documentation, and some status of the test. Yet, in many occasions, every crap is on screen. I guess the reason is that during development it's good to see everything at one place, but in a shipped product? It's not so great effort to arrange stuff into tabs. One major obsatcle for better GUI design is in Labview itself, the lack of proper widget anchoring. You either have to make ugly hacks on the front panel (that may just fail for whatever reason) or implement every positioning in code. That's a huge issue.
  5. I have a better suggestion. Place a full-window Stop button behind all other GUI elements, so whenever the manager accidentally clicks off an element by mistake: sadness.
  6. The context is Labview. I haven't seen much (any?) good looking Labview GUI examples. I know Labview means industrial HMI most of the times, but it's also good for some other related things too. But this is just a Lounge topic, I'm not gathering resources in general, I believe my GUIs are more on the good side of the UX scale. Maybe I should tweak the topic a bit, and ask: Do you guys also see that Labview GUIs in general tend to be quite ugly? Cluttered, full with unimportant info, not responsive (window resize, pane resize) even if seemingly made for desktop? And full of not user friendly solutions (like no Cancel, choosing save paths before starting a test and perhaps always defaulting to some folder, punishing user for its mistakes, no saving of GUI values, etc.). Or can you share some better designs (your own or what you found over the web). Google doesn't have so nice hits. I'll try industrial HMI in general, maybe it'll have better results. but I', also curious about other usages of Labview, like data visualization or whatever. If there is a tendency that LV GUIs suck, what could be the reason? Just for fun.
  7. I usually keep the stop button (and name it "exit" because that makes sense...). Only because of mere laziness. But I don't really see it as a biggie... If that's the managers biggest issue, then make him that stop button and everyone wins. I don't have many clients (they are my co-workers..), one of them interestingly claims that the GUI is too structured and wants to see all crap at the same time. Because 24" ultraHD can handle it. Um... no. Interesting how badly designed production line application GUIs can be. So few engineers have sense for design...
  8. Hi all! Do you know/have some nice GUI designs or examples? In google search, awesome or clean equals cluttered. I guess tab control means unawesomeness... I'd love to see nice stuff. L.
  9. Hi all! I have a strange bug/feature with Front Panel - Get image. The image has a false color. I haven't tested with other colors, I hope there's some easy answer, or it is a known bug, so I stop searching and heavy debugging and go with the alt+printscreen emulation method instead of get image. The false color is on the graph > plotimages.back and seemilnly it's only the orange that turns into pink. (Don't mind the other small differences betwen the images) The pictures are generated in sequence without any delays, maybe the front panel is not fully updated before the capture? Which would mean some things are updated asynchronomously, which I didn't explicitly do. I certainly see the front panel flashing in the right colors. Thanks for any hints!
  10. In case summing array elements then dividing with the array size, there can be overflow error if the array size is big (or whatever size). Maybe lvanlys uses the cumulative average method or whatever it's called. In short, don't use that "dumb" mean algorithm.
  11. I wanted a free solution, pretty strict corporate rules...
  12. No, but I'm not talking about booking Labview projects' workhours, just projects in general which are organized simply with folders.
  13. Thanks! Stupid question, I'll look into it of course, but could that C code you linked be dumped in a C node as it is with all the includes and stuff and then hapiness, or it's not that simple? Command line options sublick throws 404...
  14. Hi all! Is it possible to get which folders are open in all the File Explorer windows? I'd make a simple folder activity monitor program to monitor my own activity, and monitoring which folders I view would be sufficient enough for this. I know, I should be disciplined with documenting my own work hours per project but I'm simply not. It only has to work with Windows10. Thanks for any hints in advance!
  15. Pretty much nothing. Every once in a while some used monitors you can get for a fair price. And you can bid for old laptops with hard-drive removed. I took 1-2 too folders too, I'm worried that we didn't made a delivery note about them... I guess every junk the company (which employs 500+ white collars, 2000+ blue collars) makes is deliberately placed on top of coral-reefs and into the noses of whales by the management.
  16. Never mind, maybe I used File/directory info.vi.
  17. I looked at the code and one question (with low relevancy to the thread): Isn't get file size slow? I remember it being almost as slow as to read the whole file. Or did I do something wrong? Would listening to End Of File error be a better option or it has some caveats?
  18. I honestly don't understand how it can work at all, I didn't test your code (for some reason drag-dropping the snippet doesn't work for me). Your signal arrays doesn't match: Y is the original signal while X is the common concatenated and sorted time, so it can even be 0,0,0,0,1,1,1,1,2,2,2,2 and so on. And you fed this to the interpolator, no wonder it might behave strangely depending on the test data. But even if it doesn't look strange, your code will produce wrong results. Did you try my code? It's not a big change to implement.
  19. Forget my previous reply, I was in a rush. The loop where you use the interpolation is wrong, because of different array lengths. Y and X should be of same size for Interpolate 1D.vi. The time channels for each device should be fed to the Interpolate 1D.vi, not the concatenated time channel. You shouldn't build a 2D array from your raw signals anyway (what happens if your different devices are not in sync and array lengths differ?), you should compose it as an array of clusters, and each cluster should be of the time array and the signal array. It will be easier to work with that and easier to put them on graph. I can't comment on your common time channel generator code, I guess you tested it and is okay. Since the time is "commonized" and everything will have the same length, the interpolated signals can be put in a 2D array.
  20. How about usig Threshold 1D array instead? Timestamp-by-timestamp linear interpolation.
  21. Never mind. I've just tried the Decode Image Stream thing, and it doesn1t halt the main GUI, it runs like a charm. But seems to be slower than the native read JPG. I guess that's the prize of a responsive GUI. Thanks again!
  22. A related thing: I noticed that the "read JPEG file.vi" (the native one) runs in GUI thread. Is it an expected behaviour, is it the same with any file loading in Windows or am i doing something wrong? I narrowed down this GUI thread problem to "read JPEG.vi" (I replaced it with a simple 5 second wait). It is clear that the read causes the loop run in the GUI thread: with jpg read the main GUI freezes at every jpg load, with dummy wait, the main GUI is responsive without any hiccups. The read jpg is burred in subVIs, so it's not that the prioritry or preferred execution system are set up wrong for the subVIs.
  23. Thank you, that's exactly what I was looking for. I'll come back when I'll have time to implement this. If someone is into spagetti.
×
×
  • Create New...

Important Information

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