"NELSON,GARY" <gary.nelson@avagotech.com> wrote:
>
> Regarding the io file, saving the configuration with the program is
> one solution, it does not work very well with our current system of
> instrument drivers and rack configurations. I could probably make it
> work, but I would rather be able to point the programs at some known
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> location that would be in the same location on every system...
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
vee -veeio \known serverknown shareknown io file
works very well. I pretty much never use ebmedded IO since it makes the program non-portable.
Stan
--------------------------------------------------------------------------
Stan Bischof Agilent Technologies 707-577-3994 stan_bischof@agilent.com
--------------------------------------------------------------------------
---
You are currently subscribed to vrf as: ming_meng@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
>
> Regarding the io file, saving the configuration with the program is
> one solution, it does not work very well with our current system of
> instrument drivers and rack configurations. I could probably make it
> work, but I would rather be able to point the programs at some known
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> location that would be in the same location on every system...
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
vee -veeio \known serverknown shareknown io file
works very well. I pretty much never use ebmedded IO since it makes the program non-portable.
Stan
--------------------------------------------------------------------------
Stan Bischof Agilent Technologies 707-577-3994 stan_bischof@agilent.com
--------------------------------------------------------------------------
---
You are currently subscribed to vrf as: ming_meng@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
Thanks for your responses to my rant. Seems that a lot of folks are more interested in defending Vee then in adding to the rant, a good thing I think.
Here are the reasons for some of the things that folks have questioned in no particular order…
I want local user functions to clean up the program explorer. It would be similar to declaring a private function in other languages. User objects are not the best solution as you cannot make multiple calls to user objects. My solution to this ‘problem’ now is to group names by prefix for instance all functions related to a User function called ‘test_Main’ would start with the prefix ‘test_’. Another reason for this is to allow functions to use variables that are local to context to the top function or object. I believe that it is good coding practice to never use global variables. With the current scheme a user object in main that calls a local function has to use a variable that is local to context on the Main level as opposed to local to context in the object itself.
I use start buttons in objects and functions so that I can debug code easily, if you have a fairly complex program you certainly do not want to be re-starting the entire program all the time to debug a section of code. I like to have things lined up straight, having to right click to move the stupid buttons is very annoying also OK buttons do not function like start buttons I am not sure how I would use an ok button for debugging. Anyway the start buttons are not as annoying as trying to move stuff on a panel.
Instancing a function would be so useful I have hard time seeing why it would be questioned? When you need it you need it. Multiple GUI panels of various numbers depending on the situation are just one example.
Regarding the io file, saving the configuration with the program is one solution, it does not work very well with our current system of instrument drivers and rack configurations. I could probably make it work, but I would rather be able to point the programs at some known location that would be in the same location on every system…
Regarding the program explorer here is an example of what I am talking about:
It is late at night and I am trying to get some code running and the old eye balls are burning out of their sockets… I have a lot of User Functions and objects open and a lot of stuff stored in my tiny brain. I realize that I need a call to a function in an imported library… No problem, go to the program explorer and click on the vertical scroll bar, dang it click again and chase the stupid slider all around and ‘Oh No’ the user object I was working on is covered by a User Function I was not working on (my head hurts) Ok close that one go back and find the library and another User Function I was not working on pops up. Arrrrgggggg!
Regards, Gary
---
You are currently subscribed to vrf as: ming_meng@agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".