Jump to content

Eric BOBILLIER

Members
  • Content Count

    29
  • Joined

  • Last visited

  • Days Won

    1

Eric BOBILLIER last won the day on April 27 2011

Eric BOBILLIER had the most liked content!

Community Reputation

0 Neutral
  1. Hi You are right. Current View Reference isn't useful. But Invoke node "GetActiveViRef" is finally one bad solution and for at least two reasons: 1) That's not run in exe (see my previous post) 2) If you have one another vi run in parallel with the launcher, and if you click on it, this view become the Active VI and when the cursor modification is proceeding, it's in this view than the modification operate. Or you can loose the cursor release, in this case the cursor stay idle when you go back to launcher VI. Eric
  2. Finally my previous solution do not run with EXE. I propose one 2nd solution who run, but i'm not very satisfy with it because you need to modify launcher. JKI STM Cursor error.vi Launcher.vi
  3. I have found one bug with cursor set fonction , when JKI StateMachine is loaded in subpanel. Ihave made two vi for test and find one (imperfect) solution. (see my comments in cursor set step). Launcher.vi JKI STM Cursor error.vi
  4. no one to tell me if my QD works and if Vipm package is ok ?
  5. Don't worry , it's already forget... I didn't know this feature of your QD (where is it documented ?) I have test it today, and don't take it wrong, but i prefer mine . With mine you can easly * Show arguments and select them without write somethings. * Add comments or block comments in string cste. * Move the order of the state in string. * Lock one or few states (right click on right list of states). * Replace one state by another (with replace button). * Add arguments case without get out of QD (right click in arguments list). * Use drag and drop or button for case selection. * Make multi selection to move, del, lock,... * And at the end obtein string cste with differents colors for states,arguments and comments (or lock cases ) to be more readable. Please,try it and tell me what you think about and if Package is ok or not.
  6. Hi Jim Thanks for your reply, but i find it a bit agressive (maybe it's about translation,i'm french). Don't worry, i don't want to compete with you and rob of your status of best QD . I know your Case select RCF and find it very pratical (i use 3.0.0.4 version because i'm always in LV2011). I'm not agree with you and thinks than you can't compare our tools. the only things i have found who seem near, is the capacity to create case in JKI stm. And if i look in detail, yours create one empty case,while mine create one complete JKI Stm Case (with wire, background color and Add state to queue.vi). And i don't think your QD can edit string constante and populate it like do my JKI state editor. Perhaps in your last upgrade version, have you introduce those features ? Have you tested my tool ? if not, you can see here there is some old videos who show how it works. As soon as I get time,I try to update those videos to explain all features of my tool. Eric
  7. Hi JKI STM users After few years of resistance to Quick Drop usage (i always prefer JKI RCF), i have decide to create one QD who include my previous JKI STM tools. Before propose it to the QD community, I need somes beta testers to valid the package and the QD too. I have test it on LV2009 and LV2011, and all to seem to be ok (on my PC). This QD include 3 tools: 1) JKI STM editor 2) JKI STM add states 3) Remover off unused "add State to Queue.vi" Is it easy to use. 1) For JKI STM editor: Select in first one string constant connect to one "add State to Queue.vi" and launch QD with Ctrl+SpaceBar and Ctrl+K this tool open and you can easily select populate string constante with existing states. 2) For JKI STM add states : Select in first the most case structure and launch QD with Ctrl+SpaceBar and Ctrl+K This tool open one dialog to add states or separators. 3) Remover off unused "add State to Queue.vi": Don't select anything and just launch QD with Ctrl+SpaceBar and Ctrl+Shit+K This can take few seconds of wait before end. After installation of package with VIPM, it be good to recompile _JKI STM Tools folder in QD Plugin folder. I don't find how do that automaticaly with VIPM Perhapse the _ lock the vipm process for mass compilation.?? If you all ready use K letter for your QD, it is easy to modify this short cut by editing documentation of K.vi (and vi name too). I have use K.vi to be compatible with LV2009 User. Best regards Eric Bobillier ebc_qd_jki_stm_tools-1.0.0.10.vip
  8. Hi Michael I have see that on "Eyes on Vis" forum: Making the Most of New User Event Features in LabVIEW 2013 - Michael Aivaliotis, JKI, Product Manager Event-based programming is a recognized best practice in software development, and it is particularly important in LabVIEW, where nearly every significant application uses multiple loops and multiple pieces of hardware. Watch a Certified LabVIEW Architect and LabVIEW Champion demonstrate how User Events work, how JKI uses them in every project, and how they are even better in LabVIEW 2013. Also explore Version 2 of the famous JKI State Machine featuring dynamic event registration. (Session ID: TS1761) Like i don't have see your presentation on NiDays, will it be possible to have details about Version 2 of your JKI-STM ? Best regards Eric
  9. Hi Mickael it was just after licence agreement panel when lv9 is launch. But Finally, today all seen ok and package install run good. apology for this false problem. Eric
  10. Hi Today i have try to upgrade one package (NI Asynchronous Message Communication (AMC) Library to LV2009 with VIPM2013, and LV2009 start and crash. I have upgrade with success other VIPM package (like openG), but only AMC package create this problem. I have install AMC in LV2011 with success too. Another thing is when i verify connection between VIPM and LV2009,LV2009 start and crash too. Best regards E.Bobillier
  11. Hi JKI STM users Today i have update my jki state editor RCF plugin. see here New features. * Now String States constant always grow at left and justify left when modify. * Now only case structure connect to argument tunnel populate arguments list. * You can right click on arguments list and add one case not previously define. Run only if one case structure allready exist and connect to argument tunnel. * Now String constant is colorize with different colors for arguments, comments and lock states when you update it. Like that string constant text become more readable. Colors can be configure in Rcf options. Result can be something like that: Eric
  12. Hi JKI Team I have develop two new vi's for jki state machine structure. It's a "skip Until state" and skip_FromTo_State" Vi's. Those vi's skip few states in queue state list. I find them usefull when you want to skip few states in queue. See my example to understand. I wait your comments and perhapse on inclusion in future release of JKI state machine package. Regards Eric Skip_Until_JKI_State_Machine.vi Skip_FromTo_JKI_State_Machine.vi Skip_FromTo_JKI_State_Machine Example.vi
  13. It's a little off topic, but can you explain me how you add Vi Tester icon button in the project menu toolbar. Eric Project icon menu.bmp
  14. Hi JKI Team and all I Have update my Add JKi Frame Rcf PlugIn. Eric Add_JKI_Frame.zip
  15. Hi JKI Team and all I want propose two new RCF plugins that i have develop during this week. The first is " Add JKI Frame" who add a new frame in the JKI State machine after the frame where you are. This frame is a copy of the Core Frame . The name is contextual too. The seconde is "Clean JKI State Machine". This plugin remove all unnecessary Add State(s) to Queue__jki_lib_state_machine.vi (who have only one input used), and replace they by wire. Unzip the two files in RCF\Plugin folder Save in LV2009 Enjoy Eric Clean_JKI_States_Machine.zip Add_JKI_Frame.zip
×
×
  • Create New...

Important Information

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