> currently pyvcp runs when AXIS is run, but the modifications to make it > run standalone with a use-specified input file are small. I (or someone > else) just have to modify the parser to take an optional input argument, > and create a root window when AXIS does not do that.
this brings up another thought. currently when running pyvcp under AXIS, the pyvcp pins are created with names like axisui.<something> presumably, when running pyvcp standalone, pins are named pyvcp.<something> I think it would be desirable to have them named identically in both cases. That way a user can rapidly test and refine the widget layout/HAL connections in standalone mode, and then "dock" the panel into AXIS without having to modify the HAL script. Jeff, Chris: is this doable? AW ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
