Jump to content

PiDi

Members
  • Posts

    85
  • Joined

  • Last visited

  • Days Won

    15

Everything posted by PiDi

  1. I haven't seen this since around LV2013 (or 12?). In my case this was connected to very obscure compiler error, which was disabling LabVIEWs ability to build anything afterwards. LV would throw generic error window with something like "GenIL error" and after that boom - no build would ever work again. Bad news: the only way to fix this was to wipe the computer clean and reinstall everything (even "clean" uninstallation of NI software didn't help). Good news: this is probably some other problem somewhere at the initialization of the build, as the one I'm talking about is supposedly fixed long time ago. Have you tried to enable "Generate build log file" in the Advanced page of the build? Or just clear LabVIEW Data folder again?
  2. Put all your classes in libraries. (I know it might contradict what others say about NOT putting classes in libraries, but it's worth a try. Also, I have all my classes in libraries and haven't seen this error for a long time).
  3. I have no experience with that, but quick googling led me to this: http://www.topazsystems.com/msoffice-plugins.html - maybe something like that would be solution for you, as you're already creating reports in Excel?
  4. There is no direct method. BUT we can always hack something. I've attached a little plugin that allows you to change the default name of the newly created VI. It's based on project providers magic, so use this at your own risk (this is the dark magic we're talking about here ). Instructions: 1. Install this package. 2. Go to <LabVIEW>\resource\Framework\Providers\DefaultNamesChanger folder 3. Open DefaultNamesChanger.ini file. 4. Edit "VINameTemplate" key. 5. Save the ini file and restart LabVIEW. pidi_lib_defaultnameschanger-1.0.0.6.vip
  5. Have you cleared both compiled-code caches, i.e. 1. The one in <National Instruments>\LabVIEW XXXX\VIObjCache\(...) 2. The one in <Documents>\LabVIEW Data\VIObjCache I think the recovery files are also somewhere in LabVIEW Data folder... Maybe just try to wipe this whole folder? Also: the crashes at the startup happens when LV have problems with loading project providers. Any toolkit you've installed recently? Or just go to the <LabVIEW>\resource\Framework\Providers\GProviders folder and remove it's contents to see if LV will start without them, this will narrow down the problem.
  6. That's just the way it is, move along (and remember to always check at least some of your enum instances after editing). In LV2014 they added this to help: http://zone.ni.com/reference/en-XX/help/371361L-01/lvhowto/manual_update_typedef/ My collegue claims that editing enum elements in Enum Properties window is better than editing in-place using ctrl+click on the control (i.e. value resetting doesn't happen so often) - but I'm not sure about that.
  7. I remeber having similar problem when I flattened waveform on RT and then unflattened on Windows. The RT version of waveform did not contain varian with attributes, and Windows version expected this variant. Check your datatypes, something like that is easy to miss.
  8. LV 2015 SP1 - there is CCSymbols tag in "Get Tag Names": Are you sure you're operating on right ProjectItem (i.e. "Root")? (GetSymbols.vi also works if I connect Root as ProjectItem)
  9. Most, if not all, "statefull" VIs in vi.lib use while loops with continue if true option (examples: whole Point-by-Point pallete, filters in Signal Processing). OpenG follows the same convention. There is an old thread here: http://forums.ni.com/t5/LabVIEW/Execution-speed-feedback-node-vs-shift-register/td-p/295536 which points out that shift registers are faster than feedback nodes (the benchmark VI attached in second post there still shows that in LV2015 SP1). I don't have LV2017 installed, but it would be interesting to see which implementation of "Is Value Changed" is faster.
  10. SVN with TortoiseSVN for commercial projects. Git with TortoiseGit for other projects. The more I use it, the more I like it - especially for things like local commits. I can commit "in-progress" code without worrying of breaking someone else's arrows
  11. G Code Manager is now available at GitHub! You can find it here: https://github.com/veritechpl/gcm Feel free to contribute!
  12. Version 1.14.0 is added to the first post. Fabiola suggested that it should open automatically when the project is opened, so you don't forget to actually use it. Fair point, so now we have GCM up and ready when the project is opened! If you don't like it though, you can turn this feature off in new settings screen: Also: here's the build specifications editor which I've mentioned. It works with exe and installer build specs and currently allows to change the version (with a little issue with Auto-increment option, described on the panel). Just download and install it, it should show up in GCM after installation. veritech_lib_gcm_build_spec_editor-1.0.0.8.vip \
  13. Sorry to keep you waiting, but here it is: GCM 1.13.0 is available to download in the updated first post. A few highlights: 1. Updated interface, it now takes a bit less of your precious screen space and looks just the same bit better (also - with the fancy Stay on top? button, thanks for the idea TMa!): 2. New VI Execution Properties plugin (might have some issues, please let me know if you find any). Thanks to Dawid for help. 3. New VI Window Properties plugin (might have some issues, please let me know if you find any). Thanks to Dawid for help. 4. Added support for build specifications. The build specifications plugins that I mention before will be here soon (soon as in "a week or two", not as in "few months" ) 5. And global thanks to May for flat controls and general UI ideas. Download, install, use, have fun
  14. More general idea: prefer composition over inheritance. Inheritance is the strongest relationship in OO-world ("something IS something else") and should be used sparingly. It introduces high coupling, and thus lowers modularity and flexibility of the design. It can be usually avoided by using composition. For example, if you're in need of extending concrete class features or replacing some functionality, instead of inheriting from concrete class (as in AQs statement) you can use proxy pattern. Another one I like is tell, don't ask, which acts as sanity checker whenever I'm creating accessor or doing something with the data that belongs to the object outside of this object.
  15. If the dialog has only "Cancel" button (e.g. processing something with possibility to abort), I'd go with Cancelled output, because that's really the only action the user can do. If it has "Cancel" and "OK" buttons, I'd go with OK output - positive logic is generally easier to grasp when you analyze the code. However, this really depends on the context. And you can also ouput enum with "Cancel" and "OK" elements.
  16. Out of curiosity I've looked for any restrictions that NI put on their FPGA module in licence agreements. All Xilinx EULAs provided with NI software have following note: Fair enough, you can't use any Xilinx tools without LabVIEW. But what's the "licensed use"? Is it limited to NI hardware? Interestingly, I can't find any restrictions for the usage of FPGA module in my LV2015 SP1 installation. There are very specific limitations in some documents "in the Internets" - like the one here, apparently from 2009: As I said, I can't find anything like this in newer documents. So either NI waived this restriction or it's still there but now it's abstract enough so you need an army of lawyers to decipher it (as a matter of fact, the "license" folder in NI software would need an army of lawyers anyway ).
  17. I think I'll just do what LabVIEW currently does - I'll let you set it and it'll break your VI Easy - there is VI property "Inline Is Allowed", so if it will return false, I'll just disable Inline option.
  18. You mean like that? \ I have it on my feature list, +1 point for it.
  19. Hi Porter, I'm happy to hear that! Do you have any specific expectations for the next versions? Any features you'd like to see? I have one cool feature coming already: the build specifications editor. So far it doesn't look very impressive, but everyone who's ever waited for LV to open exe/installer properties will understand this plugins hidden beauty
  20. New version 1.11.0 is added to the first post. In the v.1.10 there was synchronization issue between plugins - after editing the icon with Icon Editor plugin, it wasn't updated in Basic Documentation, and vice versa. This is fixed now by making some changes to the events that plugin receives. I'll probably review the communication with plugins a few more times, so if you're trying to develop your own plugin and run into any problems - please contact me. I've also updated the "Your own plugin" part in the documentation (now with fancy sequence diagram!). So, not many fireworks in this version, or at least the fireworks are hidden somewhere in block diagrams.
  21. Looking at my GCM topic: Here are the problems I've noticed: One more thing: attachments with icons and download counter was nice, can they come back?
  22. I've just uploaded new version 1.10 (see the updated first post). It comes with new plugin - Icon Editor, which currently allows to clear icon and edit its text: I'm using this quickly edit my class members, when I don't have time to create fancy icons with glyphs. You can always double-click on Icon to open native Icon Editor. At this moment I see 42 downloads of the first version, which is great But I'd love to see more feedback from you! If you have any comments, issues, propositions, requests, questions, or you just like it/don't like it, or you don't know how to use it, let me know by commenting here!
  23. Hey, Stobber, thanks for the reply! 1. We've been using this tool for some time at Veritech and I finally got myself to show it to the Community - I also presented it at the European CLA Summit just before posting it. If you like it and you think that it can save just a little bit of your precious time - that's fantastic! 2. Hmm, no, I can't give you any good reason for that other than "we've just chosen it and then moved on to our normal work". We've had a similar tool once which we called LabVIEW Code Manager, than this one took this name, then we renamed it to G Code Manager, so we won't have proprietary LabVIEW name. But I never thought why is it actually "Code Manager", and now you've got me to rethink the name again 3. Yes and Yes. One of the main reasons I released it is that I want to get some good feedback to boost the developement. As for the community collaboration - I'm happy to hear any suggestions on any level, from bug reports and features requests to any architectural tips and minor tweaks somewhere deep in the code. Oh, and I forgot to mention few things about it: - you can open the main VI block diagram by pressing CTRL+SHIFT+E. - you can open any plugin BD by right-clicking on empty space in the plugin and selecting Open Block Diagram (this is subpanel). - none of the code is password protected - it is intended to be free, open-source tool under GPL licence - the code will be posted on github sooner than later (or as soon as I find some time to do it)
  24. Known issues v. 1.9.0.54 Any editions (VI/Class description, icons) might not save after the project is closed.Workaround: To ensure saving all the changes, use the Save All button in Project Explorer: Comment: I did not noticed that because my normal workflow includes bashing Save All button whenever I'm done with anything (and sometimes just randomly)
×
×
  • Create New...

Important Information

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