Jump to content

Philippe Guerit

JKI Team
  • Content Count

  • Joined

  • Last visited

Everything posted by Philippe Guerit

  1. It could be that another application is using port 3363 on your machine. Can you try a few different number (on both LabVIEW and VIPM) to see if this help? Note: you can find the list of all the listening ports by running (as an administrator) "netstat -a -b" in a command line prompt. Alternatively you can use Microsoft Sysinternals TCPView (which is graphical and update in real time). Thanks
  2. I am not sure what you mean by "it will empty the queue", but here is what you should do. Make sure that you have a timeout different from -1 for the event structure (ex: 100) Make sure that you append in the front of the queue Make sure that the remaining state is connect to the state in of the "add states to queue" vi in every frame (this could explain your empty queue). If you do all of the above, this should work fine. Below is a screenshot and an example written in LabVIEW 2010. Hope it helps. Philippe SM question.vi
  3. It look like you are correct. The undo transaction does not works on string constant that were modified via scripting (even in the case of the RCF plugin the string re sizes itself and it appears that the undo worked, but it actually did not). You might want to report this on the LabVIEW API group. Correction: I see that you already did it. PJM
  4. Eric, I found another bug. Here is the work flow to reproduce it: Edit a String (in the JKI state editor) Update the string on the BD Close the JKI state editor Undo the editing in the BD (CTRL+Z) Reopen the JKI State Editor --> You see the previous content (prior to undoing) Expected behavior: You should see the current content. Philippe
  5. I was about to tell you about that bug. Glad you found it. Here is another one for you. You should use the option that was read from the ini file and not the hard coded constant (in the menu activation frame). Philippe
  6. Whoa, I love it! One comment: Can you replace all control with system one and use the system color as a background color? Thanks Philippe
  7. Dan, What kind of window installation is that laptop running? Is there anything out of the ordinary? Thanks Philippe
  8. Did you try to uncheck the option "Check for new version of VIPM at startup"? Philippe
  9. No, but VIPM has its own "build hook" that you can use to manipulate the build output (such as adding your own documentation for instance). For more info about it, see the online help here. Philippe
  10. Ton, This is an interesting idea. This would allow the state machine to exit even when an error occurs. Philippe
  11. Here you go (7.0):_jki_lib_state_machine.zip Note: Copy this somewhere in your user.lib folder Philippe
  12. Dave, Have a look at this Blog article A Early Look at VIPM Enterprise Edition. Excerpt: "..That’s why the next release, which we’re calling “VIPM Enterprise Edition“, is going to focus on features that will enable a team of LabVIEW developers to share packages easily..." Philippe
  13. Yes, I believe that you have to start with a control from LV 7.1. (as it says in the video). Philippe
  14. Glen, The fact that you do no longer get a log file is information by itself. Thanks again for the info. Philippe
  15. Glen, Thanks for the log file. We will try to see if we can replicate this and fix it. Out of curiosity, what kind of screen resolution are you running at on your linux box? Do you have multiple monitor? Philippe
  16. Glen, I am sorry to hear that. Please look in the folder where you install VIPM for a subfolder called Error. You should see a timestamped error log with more info about the issue you are experiencing. If you could post it here this might help. Thanks Philippe
  17. I have had this happen to me as well even when I was not using VIPM. So I am not entirely sure that the /tmp access right changed is due to VIPM (although I do not discard it). Like you I was confused when I could not reboot back to my KDE. But thanks for the information. we will look into it. PJM
  18. Neil, I believe we have identified the issue and a possible fix will be available in the next bug fix release of VIPM. Thanks for your patience. Philippe
  19. Neil, Could you tell us more about your system? What OS are you running? Do you have an antivirus, a firewall? How old is the computer? How much memory does it have? Additionally, what happen after the progress bar run through the end? Did you wait some more? Also, do you have enough space left on your hard drive where your temporary folder is located? If you could post a screenshot, this might be useful as well. Thanks again for the feedback. Philippe
  20. I think I have heard of this happening before. I think somehow somebody has a lock on one (or more) of the file(s) being installed. Could you tell us roughly when in the installation process this happen (when did you saw the blue progress bar jump or hang before you got the error message? was that around 25%, 50%, 75% or close to the end?)? There might be some way for us to mitigate this if we could pinpoint when this happened. Thanks Philippe
  21. I agree and this is on our to do list. As of now you can just uninstall and re-install the same package (you don't have to do a downgrade). Philippe
  22. Ya, this form is a great motivator (feel free to complete it more than once). Philippe
  23. Lars, Looking at your screenshot I can see a few things that might go wrong. First the EasyXML reader already does the parsing, so there is no need to call the parser again. Second for the reader (or the parser) to work you have to connect your cluster of data to the type input. Look at the attached screenshot of your code below. Try to apply the same change that I made (in the red rectangle) to your original code and let us know if this help. Good Luck. Philippe
  24. kmous, This forum is not the right place to ask general LabVIEW question. Instead ask your question on LAVA or on NI Forum. Thanks
  • Create New...

Important Information

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