Menu
▾
▴
opengtoolkit-developers — OpenG Toolkit developers mailing list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(53) |
Nov
(66) |
Dec
(24) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
(5) |
Mar
(72) |
Apr
(15) |
May
|
Jun
|
Jul
(10) |
Aug
(2) |
Sep
(18) |
Oct
(2) |
Nov
|
Dec
(6) |
| 2005 |
Jan
(41) |
Feb
(28) |
Mar
(14) |
Apr
(18) |
May
(10) |
Jun
(6) |
Jul
(5) |
Aug
(1) |
Sep
(3) |
Oct
|
Nov
|
Dec
(1) |
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
|
From: Brian G. <bri...@da...> - 2005-03-18 21:40:20
|
Hello OpenG Developers, LabVIEW Version Chooser is a great application for anyone that develops = with multiple versions of LabVIEW and/or uses files from different versions = of LabVIEW. The following link has a complete description and screen shots http://www.dataact.com/LVC.htm To show support for OpenG, we are offering complimentary license keys to anyone that has contributed to OpenG. To get the key, just fill out the registration and include "OpenG" in any of the non required registration fields (such as Organization). You can download the latest version here http://downloads.dataact.com/LVC-1.0.8.334(beta)-setup.exe We hope that you find this application useful and thank you for all of = your hard work in bringing open source software to LabVIEW. Please send any feedback or feature requests directly to me. Sincerely, Brian Gangloff President Certified LabVIEW Developer DataAct Incorporated 375 Westminster Rd, Suite 300 Rochester, NY 14607 585.802.6036 bri...@da... http://www.dataact.com |
|
From: Jim K. <jim...@ja...> - 2005-03-18 17:21:42
|
Chris, You should be able to download the packages using OpenG Commander. If = you are seeing TCP timeout errors, try changing your selected package mirror = to one of the others. The default (voxel - new york) appear to not be = working well. I have found that the (easynews - arizona) is working well. In = the next release of Commander we are going to have a much better system for automatically iterating through the mirror list when there is trouble connecting to the selected mirror. Also, we are going to have a system = that allows automatically downloading updates to the mirror list. Commander should have no trouble installing the ogfwk_opengoop-0.10-1 package. I'm not sure what the problem is. You might want to post = specific details and screenshots to the Commander support forum at http://forums.openg.org Regards, -Jim > -----Original Message----- > From: ope...@li...=20 > [mailto:ope...@li...]=20 > On Behalf Of Christopher Relf > Sent: Thursday, March 17, 2005 6:25 PM > To: ope...@li... > Subject: RE: Time to get involved... >=20 > Sorry for posting to the developers list everyone - I replied=20 > to an email > from Jim without looking at where it was going :) >=20 > That said, I've worked out that the old OpenG packages can=20 > only be installed > using the old package installer - are the old packages being=20 > changed so the > new commander can use them? >=20 > Ta, > Chris >=20 > --- > EULA > 1) This is a private email, and although the views expressed=20 > within it may > not be purely my own, unless specifically referenced I do not=20 > suggest they > are necessarily associated with anyone else including, but=20 > not limited to, > my employer(s). > 2) This email has NOT been scanned for virii - attached=20 > file(s), if any, are > provided as is. By copying, detaching and/or opening attached=20 > files, you > agree to indemnify the sender of such responsibility. > 3) Because e-mail can be altered electronically, the integrity of this > communication cannot be guaranteed. >=20 > -----Original Message----- > From: Christopher Relf [mailto:chr...@ya...]=20 > Sent: Friday, March 18, 2005 1:18 PM > To: 'ope...@li...' > Subject: RE: Time to get involved... >=20 >=20 > G'Day Jim, >=20 > A quick question - I'm trying to get into OO a bit=20 > more, and thought > I'd give the OpenG GOOP toolkit a bit of a look. I've downloaded > "ogfwk_opengoop-0.10-1.ogp" from the old OpenG website (I=20 > couldn't find it > on the new one), but I can't install it through the new=20 > commander. What am > I doing wrong? >=20 > Chris >=20 >=20 > --- > EULA > 1) This is a private email, and although the views expressed=20 > within it may > not be purely my own, unless specifically referenced I do not=20 > suggest they > are necessarily associated with anyone else including, but=20 > not limited to, > my employer(s). > 2) This email has NOT been scanned for virii - attached=20 > file(s), if any, are > provided as is. By copying, detaching and/or opening attached=20 > files, you > agree to indemnify the sender of such responsibility. > 3) Because e-mail can be altered electronically, the integrity of this > communication cannot be guaranteed. >=20 > -----Original Message----- > From: ope...@li... > [mailto:ope...@li...]=20 > On Behalf Of > Jim Kring > Sent: Tuesday, March 15, 2005 2:59 PM > To: 'Christopher Relf' > Cc: ope...@li... > Subject: RE: Time to get involved... >=20 >=20 > G'Day Chris, >=20 > We're very glad to have you on-board the OpenG Toolkit=20 > developer team. I've > just signed you up for the opengtoolkit developers mailing=20 > list. Regarding > the addition of more Boolean controls to the "buttons"=20 > package. I think > that this is a GREAT idea. Personally, I have a lot of cool=20 > buttons that > I've been meaning to add (I've "been inspired by" a lot the FireFox > buttons), so this will be a great opportunity for me to get=20 > off my butt, > too. I recall Mike Ashe mentioning to me a while back that=20 > he had lots of > buttons that he wanted to add -- I'll ping him and see if we=20 > can merge his > into our collection. >=20 > 1st step: sign up for a sourceforge.net account and send me=20 > an email with > your username. Please also sign up for a skype account=20 > (www.skype.com) and > send me you username -- the team uses skype for IM and voice chat. >=20 > 2nd step: once I add you to the opengtoolkit project at=20 > sourceforge.net you > will need to checkout a developers copy of the "buttons" CVS=20 > module. I'll > provide you with instructions once I add you to the project. >=20 > 3rd step: in order to edit the "buttons" CVS module you will=20 > need a few > pointers on how deal with the palette menus (with respect to=20 > the MNU files > in the CVS module). For starters, please read the attached document > ("Palette Menu Editing Process.txt"). This explains some of=20 > the pitfalls > and idiosyncrasies of MNU/palette editing. >=20 > Again, welcome to the team :-) >=20 > Cheers, >=20 > -Jim >=20 >=20 > > -----Original Message----- > > From: OpenG.org [mailto:in...@op...] > > Sent: Monday, March 14, 2005 6:53 PM > > To: ji...@ji... > > Subject: Time to get involved... > >=20 > > =20 > > G'Day Jim, > >=20 > > Firstly, let me apologise for not getting onboad with OpenG=20 > > previously - I've been an active listener, but as yet=20 > haven't helped=20 > > out. That said, I've decided that it's time for me to get=20 > off my arse=20 > > and get involved :) The first thing I'd like to contribute=20 > is a bunch=20 > > of boolean controls that I use for my toolbars. How do I get=20 > > involved? > >=20 > > cheers, > > Chris > >=20 >=20 >=20 >=20 > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from=20 > real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_ide95&alloc_id=14396&opLk > _______________________________________________ > OpenGToolkit-Developers mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers >=20 |
|
From: Christopher R. <chr...@ya...> - 2005-03-18 02:24:50
|
Sorry for posting to the developers list everyone - I replied to an = email from Jim without looking at where it was going :) That said, I've worked out that the old OpenG packages can only be = installed using the old package installer - are the old packages being changed so = the new commander can use them? Ta, Chris --- EULA 1) This is a private email, and although the views expressed within it = may not be purely my own, unless specifically referenced I do not suggest = they are necessarily associated with anyone else including, but not limited = to, my employer(s). 2) This email has NOT been scanned for virii - attached file(s), if any, = are provided as is. By copying, detaching and/or opening attached files, you agree to indemnify the sender of such responsibility. 3) Because e-mail can be altered electronically, the integrity of this communication cannot be guaranteed. -----Original Message----- From: Christopher Relf [mailto:chr...@ya...]=20 Sent: Friday, March 18, 2005 1:18 PM To: 'ope...@li...' Subject: RE: Time to get involved... G'Day Jim, A quick question - I'm trying to get into OO a bit more, and thought I'd give the OpenG GOOP toolkit a bit of a look. I've downloaded "ogfwk_opengoop-0.10-1.ogp" from the old OpenG website (I couldn't find = it on the new one), but I can't install it through the new commander. What = am I doing wrong? Chris --- EULA 1) This is a private email, and although the views expressed within it = may not be purely my own, unless specifically referenced I do not suggest = they are necessarily associated with anyone else including, but not limited = to, my employer(s). 2) This email has NOT been scanned for virii - attached file(s), if any, = are provided as is. By copying, detaching and/or opening attached files, you agree to indemnify the sender of such responsibility. 3) Because e-mail can be altered electronically, the integrity of this communication cannot be guaranteed. -----Original Message----- From: ope...@li... [mailto:ope...@li...] On Behalf = Of Jim Kring Sent: Tuesday, March 15, 2005 2:59 PM To: 'Christopher Relf' Cc: ope...@li... Subject: RE: Time to get involved... G'Day Chris, We're very glad to have you on-board the OpenG Toolkit developer team. = I've just signed you up for the opengtoolkit developers mailing list. = Regarding the addition of more Boolean controls to the "buttons" package. I think that this is a GREAT idea. Personally, I have a lot of cool buttons = that I've been meaning to add (I've "been inspired by" a lot the FireFox buttons), so this will be a great opportunity for me to get off my butt, too. I recall Mike Ashe mentioning to me a while back that he had lots = of buttons that he wanted to add -- I'll ping him and see if we can merge = his into our collection. 1st step: sign up for a sourceforge.net account and send me an email = with your username. Please also sign up for a skype account (www.skype.com) = and send me you username -- the team uses skype for IM and voice chat. 2nd step: once I add you to the opengtoolkit project at sourceforge.net = you will need to checkout a developers copy of the "buttons" CVS module. = I'll provide you with instructions once I add you to the project. 3rd step: in order to edit the "buttons" CVS module you will need a few pointers on how deal with the palette menus (with respect to the MNU = files in the CVS module). For starters, please read the attached document ("Palette Menu Editing Process.txt"). This explains some of the = pitfalls and idiosyncrasies of MNU/palette editing. Again, welcome to the team :-) Cheers, -Jim > -----Original Message----- > From: OpenG.org [mailto:in...@op...] > Sent: Monday, March 14, 2005 6:53 PM > To: ji...@ji... > Subject: Time to get involved... >=20 > =20 > G'Day Jim, >=20 > Firstly, let me apologise for not getting onboad with OpenG=20 > previously - I've been an active listener, but as yet haven't helped=20 > out. That said, I've decided that it's time for me to get off my arse = > and get involved :) The first thing I'd like to contribute is a bunch = > of boolean controls that I use for my toolbars. How do I get=20 > involved? >=20 > cheers, > Chris >=20 |
|
From: Christopher R. <chr...@ya...> - 2005-03-18 02:18:10
|
G'Day Jim, A quick question - I'm trying to get into OO a bit more, and thought I'd give the OpenG GOOP toolkit a bit of a look. I've downloaded "ogfwk_opengoop-0.10-1.ogp" from the old OpenG website (I couldn't find = it on the new one), but I can't install it through the new commander. What = am I doing wrong? Chris --- EULA 1) This is a private email, and although the views expressed within it = may not be purely my own, unless specifically referenced I do not suggest = they are necessarily associated with anyone else including, but not limited = to, my employer(s). 2) This email has NOT been scanned for virii - attached file(s), if any, = are provided as is. By copying, detaching and/or opening attached files, you agree to indemnify the sender of such responsibility. 3) Because e-mail can be altered electronically, the integrity of this communication cannot be guaranteed. -----Original Message----- From: ope...@li... [mailto:ope...@li...] On Behalf = Of Jim Kring Sent: Tuesday, March 15, 2005 2:59 PM To: 'Christopher Relf' Cc: ope...@li... Subject: RE: Time to get involved... G'Day Chris, We're very glad to have you on-board the OpenG Toolkit developer team. = I've just signed you up for the opengtoolkit developers mailing list. = Regarding the addition of more Boolean controls to the "buttons" package. I think that this is a GREAT idea. Personally, I have a lot of cool buttons = that I've been meaning to add (I've "been inspired by" a lot the FireFox buttons), so this will be a great opportunity for me to get off my butt, too. I recall Mike Ashe mentioning to me a while back that he had lots = of buttons that he wanted to add -- I'll ping him and see if we can merge = his into our collection. 1st step: sign up for a sourceforge.net account and send me an email = with your username. Please also sign up for a skype account (www.skype.com) = and send me you username -- the team uses skype for IM and voice chat. 2nd step: once I add you to the opengtoolkit project at sourceforge.net = you will need to checkout a developers copy of the "buttons" CVS module. = I'll provide you with instructions once I add you to the project. 3rd step: in order to edit the "buttons" CVS module you will need a few pointers on how deal with the palette menus (with respect to the MNU = files in the CVS module). For starters, please read the attached document ("Palette Menu Editing Process.txt"). This explains some of the = pitfalls and idiosyncrasies of MNU/palette editing. Again, welcome to the team :-) Cheers, -Jim > -----Original Message----- > From: OpenG.org [mailto:in...@op...] > Sent: Monday, March 14, 2005 6:53 PM > To: ji...@ji... > Subject: Time to get involved... >=20 > =20 > G'Day Jim, >=20 > Firstly, let me apologise for not getting onboad with > OpenG previously - I've been an active listener, but as yet=20 > haven't helped out. That said, I've decided that it's time=20 > for me to get off my arse and get involved :) The first=20 > thing I'd like to contribute is a bunch of boolean controls=20 > that I use for my toolbars. How do I get involved? >=20 > cheers, > Chris >=20 |
|
From: Jim K. <jim...@ja...> - 2005-03-15 03:59:00
|
G'Day Chris, We're very glad to have you on-board the OpenG Toolkit developer team. I've just signed you up for the opengtoolkit developers mailing list. Regarding the addition of more Boolean controls to the "buttons" package. I think that this is a GREAT idea. Personally, I have a lot of cool buttons that I've been meaning to add (I've "been inspired by" a lot the FireFox buttons), so this will be a great opportunity for me to get off my butt, too. I recall Mike Ashe mentioning to me a while back that he had lots of buttons that he wanted to add -- I'll ping him and see if we can merge his into our collection. 1st step: sign up for a sourceforge.net account and send me an email with your username. Please also sign up for a skype account (www.skype.com) and send me you username -- the team uses skype for IM and voice chat. 2nd step: once I add you to the opengtoolkit project at sourceforge.net you will need to checkout a developers copy of the "buttons" CVS module. I'll provide you with instructions once I add you to the project. 3rd step: in order to edit the "buttons" CVS module you will need a few pointers on how deal with the palette menus (with respect to the MNU files in the CVS module). For starters, please read the attached document ("Palette Menu Editing Process.txt"). This explains some of the pitfalls and idiosyncrasies of MNU/palette editing. Again, welcome to the team :-) Cheers, -Jim > -----Original Message----- > From: OpenG.org [mailto:in...@op...] > Sent: Monday, March 14, 2005 6:53 PM > To: ji...@ji... > Subject: Time to get involved... > > > G'Day Jim, > > Firstly, let me apologise for not getting onboad with > OpenG previously - I've been an active listener, but as yet > haven't helped out. That said, I've decided that it's time > for me to get off my arse and get involved :) The first > thing I'd like to contribute is a bunch of boolean controls > that I use for my toolbars. How do I get involved? > > cheers, > Chris > |
|
From: Jim K. <jim...@ja...> - 2005-03-04 20:14:57
|
German, I'll try to get this fixed ASAP. Regards, -Jim > -----Original Message----- > From: ope...@li... > [mailto:ope...@li...] > On Behalf Of German Schumacher > Sent: Friday, March 04, 2005 11:47 AM > To: ope...@li... > Subject: Re: "Asynchronous Call By Reference" and other > package proposals > > Hi Jim: > > This is a package of great interest to me. Unfortunately all my > attempts to login, in order to get it, fail. Could you please check > what's wrong with my registration? Maybe it's just a matter > of updating > the password. > > Thanks, > > German. > > Jim Kring wrote: > > >Hello All, > > > >I wanted to remind you all that we have a new discussion forum at > >http://forums.openg.org called Package Proposals. Before > changes or new > >additions are added to the collection of OpenG tools, we are > going to give > >everyone an opportunity to take a look at and provide feedback on our > >proposals. This will give a wide audience of people an easy way to > >contribute to OpenG, and also help us continue to provide a > high-quality > >software product for our users (meaning you!). > > > >I have just posted a new proposal called "Asynchronous Call > By Reference" > >which includes an example download and documentation of the proposed > >library. I am really excited about this library. Please > download the > >example library and provide feedback. > > > >Best Regards, > > > >-Jim Kring > > > > > > > >------------------------------------------------------- > >SF email is sponsored by - The IT Product Guide > >Read honest & candid reviews on hundreds of IT Products from > real users. > >Discover which products truly live up to the hype. Start reading now. > >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >_______________________________________________ > >OpenGToolkit-Developers mailing list > >Ope...@li... > >https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers > > > > > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from > real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > OpenGToolkit-Developers mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers > |
|
From: German S. <gsc...@ct...> - 2005-03-04 19:46:41
|
Hi Jim:
This is a package of great interest to me. Unfortunately all my
attempts to login, in order to get it, fail. Could you please check
what's wrong with my registration? Maybe it's just a matter of updating
the password.
Thanks,
German.
Jim Kring wrote:
>Hello All,
>
>I wanted to remind you all that we have a new discussion forum at
>http://forums.openg.org called Package Proposals. Before changes or new
>additions are added to the collection of OpenG tools, we are going to give
>everyone an opportunity to take a look at and provide feedback on our
>proposals. This will give a wide audience of people an easy way to
>contribute to OpenG, and also help us continue to provide a high-quality
>software product for our users (meaning you!).
>
>I have just posted a new proposal called "Asynchronous Call By Reference"
>which includes an example download and documentation of the proposed
>library. I am really excited about this library. Please download the
>example library and provide feedback.
>
>Best Regards,
>
>-Jim Kring
>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>_______________________________________________
>OpenGToolkit-Developers mailing list
>Ope...@li...
>https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers
>
>
>
|
|
From: Jim K. <jim...@ja...> - 2005-03-04 08:14:40
|
Hello All, I wanted to remind you all that we have a new discussion forum at http://forums.openg.org called Package Proposals. Before changes or new additions are added to the collection of OpenG tools, we are going to give everyone an opportunity to take a look at and provide feedback on our proposals. This will give a wide audience of people an easy way to contribute to OpenG, and also help us continue to provide a high-quality software product for our users (meaning you!). I have just posted a new proposal called "Asynchronous Call By Reference" which includes an example download and documentation of the proposed library. I am really excited about this library. Please download the example library and provide feedback. Best Regards, -Jim Kring |
|
From: Paul F. S. <Pa...@SU...> - 2005-02-20 09:06:29
|
Michael Aivaliotis wrote: >... Right now, you can undock the properties window and position it >anywhere you like. I can't find a way to do so in OS X. If I try to drag it away from the left side of the main window, it repeatedly pops back to its original position. The windows can't be overlapped and the properties window disappears if I close the main window. The only way to get the properties window on the smaller screen is to shrink the main window. -- Paul F. Sullivan ---------------------------------------------------- SULLutions (781)769-6869 "when a single discipline is not enough" visit http://www.SULLutions.com ---------------------------------------------------- |
|
From: Michael A. <mi...@ai...> - 2005-02-19 18:40:30
|
Paul F. Sullivan wrote: > This morning I brought up the window and found it half off-screen. It > appears to be docked permanently to the main window. On my customary > 1152x864 screen, I could drag the main window left and view the whole > Package Properties window, but this wouldn't work if my aging eyes > were viewing a smaller monitor at 800x600. I'll post this to the > Commander Features forum as well. Thanks for the feedback. One of the features that I want to implement is the ability for every floating window to remember its last opened position, docked or undocked. Right now, you can undock the properties window and position it anywhere you like. This allows you to resize the Main Window to something larger. This was done to accomodate the growing list of available packages. When you close down Commander it will start back up in the default positions. Also, the intent is to have Commander check your screen resolution on startup and prohibit screens from launching off-screen. Thank You Michael Aivaliotis |
|
From: Michael A. <mi...@ai...> - 2005-02-19 18:40:13
|
Paul F. Sullivan wrote: > This morning I brought up the window and found it half off-screen. It > appears to be docked permanently to the main window. On my customary > 1152x864 screen, I could drag the main window left and view the whole > Package Properties window, but this wouldn't work if my aging eyes > were viewing a smaller monitor at 800x600. I'll post this to the > Commander Features forum as well. Thanks for the feedbck. One of the features that I want to implement is the ability for every floating window to remember its last opened position, docked or undocked. Right now, you can undock the properties window and position it anywhere you like. This allows you to resize the Main Window to something larger. This was done to accomodate the growing list of available packages. When you close down Commander it will start back up in the default positions. Also, the intent is to have Commander check your screen resolution on startup and prohibit screens from launching off-screen. Thank You Michael Aivaliotis |
|
From: Jim K. <jim...@ja...> - 2005-02-19 17:55:03
|
Thanks for the report, Paul. In addition to writing the excellent documentation, Michael implemented the Commander GUIs and docking feature. Personally, I work on a 1600x1200 display, so I hadn't noticed that problem. Our goal is to support screen resolutions down to 1024x768, which I think will fit all three UI windows. Regards, -Jim > -----Original Message----- > From: ope...@li... > [mailto:ope...@li...] > On Behalf Of Paul F. Sullivan > Sent: Saturday, February 19, 2005 5:43 AM > To: ope...@li... > Cc: Jim Kring > Subject: Re: Surprise package available in Commander > > Jim, > > If I had read Michael Aivaliotis's excellent documentation instead of > just downloading it a couple of weeks ago and leaving it to read > later, I would have seen the Package Properties window and known > what I was looking for. I was relieved to notice that Michael's > manual ends before explaining the window in detail, so at least I > didn't overlook the obvious. > > This morning I brought up the window and found it half off-screen. It > appears to be docked permanently to the main window. On my customary > 1152x864 screen, I could drag the main window left and view the whole > Package Properties window, but this wouldn't work if my aging eyes > were viewing a smaller monitor at 800x600. I'll post this to the > Commander Features forum as well. > > -- > Paul > > ---------------------------------------------------- > > SULLutions (781)769-6869 > "when a single discipline is not enough" > > visit http://www.SULLutions.com > > ---------------------------------------------------- > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from > real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > OpenGToolkit-Developers mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers > |
|
From: Paul F. S. <Pa...@SU...> - 2005-02-19 16:55:37
|
Jim, If I had read Michael Aivaliotis's excellent documentation instead of just downloading it a couple of weeks ago and leaving it to read later, I would have seen the Package Properties window and known what I was looking for. I was relieved to notice that Michael's manual ends before explaining the window in detail, so at least I didn't overlook the obvious. This morning I brought up the window and found it half off-screen. It appears to be docked permanently to the main window. On my customary 1152x864 screen, I could drag the main window left and view the whole Package Properties window, but this wouldn't work if my aging eyes were viewing a smaller monitor at 800x600. I'll post this to the Commander Features forum as well. -- Paul ---------------------------------------------------- SULLutions (781)769-6869 "when a single discipline is not enough" visit http://www.SULLutions.com ---------------------------------------------------- |
|
From: Jim K. <jim...@ja...> - 2005-02-18 15:36:42
|
Paul, I'm glad you like the tool. If you open the Package Properties window of commander you will find the package description for ogrsc_compare_vi_to_disk: "Adds a 'Compare to Disk...' option to the File menu, which opens the active VI and the copy on disk in the LabVIEW comparison tool. Thanks to Ian Dees for his application 'lvdiff', from which this utility derives inspiration and code." Regards, -Jim > -----Original Message----- > From: ope...@li... > [mailto:ope...@li...] > On Behalf Of Paul F. Sullivan > Sent: Friday, February 18, 2005 7:27 AM > To: ope...@li... > Cc: Jim Kring > Subject: Re: Surprise package available in Commander (Jim Kring) > > Jim, > > I had no idea that I should look in the File menu for your new tool. > Did I miss something? How difficult would it be to put at least a > reference to it in the Tools>>Compare menu? (I guess that would be > vulnerable to NI updates and, once you know to look in the File menu, > superfluous.) > > It was well worth the effort to find it. > 1. Now I can tell with exquisite detail what I've changed > since loading the VI. > 2. AND I found the Rename Folder of VIs... tool as well! (Obviously, > I've not noticed it for quite a while.) > > Thanks, > -- > Paul > > ---------------------------------------------------- > > SULLutions (781)769-6869 > "when a single discipline is not enough" > > visit http://www.SULLutions.com > > ---------------------------------------------------- > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from > real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > OpenGToolkit-Developers mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers > |
|
From: Paul F. S. <Pa...@SU...> - 2005-02-18 15:27:45
|
Jim, I had no idea that I should look in the File menu for your new tool. Did I miss something? How difficult would it be to put at least a reference to it in the Tools>>Compare menu? (I guess that would be vulnerable to NI updates and, once you know to look in the File menu, superfluous.) It was well worth the effort to find it. 1. Now I can tell with exquisite detail what I've changed since loading the VI. 2. AND I found the Rename Folder of VIs... tool as well! (Obviously, I've not noticed it for quite a while.) Thanks, -- Paul ---------------------------------------------------- SULLutions (781)769-6869 "when a single discipline is not enough" visit http://www.SULLutions.com ---------------------------------------------------- |
|
From: Brian G. <bri...@da...> - 2005-02-18 14:50:45
|
Now I just got the "must call from the front panel" error. Here's a modification using the exposed property from the internet tools that allows the code to be called from the block diagram, the only catch is the library must be moved to the ..\LabVIEW\project\ directory. I have also included the code to remove the llb from the path which exposes the tool in the Tools menu versus the File menu (This might actually make sense, since this is where the NI compare tools are located). If anyone wants the changes, open the attached VI and save back into the library with the original name and finally move the library to the ..\LabVIEW\project\ directory. Brian |
|
From: Brian G. <bri...@da...> - 2005-02-18 14:06:32
|
Jim Kring wrote: > There is a new (surprise) package available for download using OpenG >Commander -- update your package list from the Internet and see what's new. > Great tool. I did find one issue if the VI is inside of a library (llb), the copy fails since you change the extension. There are two options, either leave the extension and add a prefix or check if the path contains a *.llb and store the copy at the same level as the llb. I would prefer the later since the first will change the modify date of the llb, which would not happen if you decide not to save the changes. Attached is a routine that gets the directory path of a VI, it works for llbs and exes Brian |
|
From: Jim K. <jim...@ja...> - 2005-02-17 08:27:43
|
Hello all, There is a new (surprise) package available for download using OpenG Commander -- update your package list from the Internet and see what's new. Once you see this great tool, you'll wonder how you ever lived without it (I'm not exaggerating :-) Regards, -Jim Kring -- Get Commander at http://commander.openg.org |
|
From: Scott H. <st...@ma...> - 2005-02-14 14:35:13
|
>Hacking the default values in the registry is not only cumbersome because of the differences between Windows versions, but it is also an ugly procedure which in fact changes the default settings a user may have defined in Control Panels, without a clear indication of that fact (and other applications might then work not anymore correctly after you run an OpenG serial driver application). But using the LV config file VIs on the visaconf file to update it before opening each port should give you the ability to set the default values before connectiing to the port. Now it still doesn't solve all the problems since the port will still get a hiccup as the parameters are set while opening but it may make it a bit cleaner. Somewhere I had a set of VIs that opened and set values in the VISA conf file, but it was trivial to set it up again. The file is all set up for the section and value keys of the config files. However it will seriously change the comments in the file. The visaconf file is 'almost' compatible with the default labview config file VIs. Now to get away from using VISA can use a similar method to change the conf file. -Scott |
|
From: Rolf K. <rol...@ci...> - 2005-02-14 08:23:43
|
=20 Albert, =20 Supporting both standards is not help readability....=20 Furthermore extending the old format for more parameters is impossible.=20 I'm not talking about serial only but all possible busses that are supported by VISA While I agree with you about the problem and the limitations for a VISA implementation, I thought this was for the OpenG serial driver (which is supposed to have an interface similar to VISA but not being VISA for the time being). As such supporting both forms isn't that much of a problem, and of course it won't work for non serial drivers once an OpenG VISA implementation might be available. That said it is indeed a serious problem to change parameters on the serial port before it is opened. Hacking the default values in the registry is not only cumbersome because of the differences between Windows versions, but it is also an ugly procedure which in fact changes the default settings a user may have defined in Control Panels, without a clear indication of that fact (and other applications might then work not anymore correctly after you run an OpenG serial driver application). So the proper way is IMO to try to work around possible problems in the driver itself by clearing the input buffers on any change of relevant serial port properties. Rolf Kalbermatter |
|
From: <alb...@ph...> - 2005-02-14 07:21:29
|
Supporting both standards is not help readability....
Furthermore extending the old format for more parameters is impossible.
I'm not talking about serial only but all possible busses that are
supported by VISA
Albert Geven Tel +31 (0)40 27
43019
Philips Research Fax +31 (0)84 722 9844
prof Holstlaan 4 WAA01 Email alb...@ph...
5656AA Eindhoven
Dou...@mk...
Sent by:
ope...@li...
11-02-2005 17:30
Please respond to opengtoolkit-developers
To: ope...@li...
cc: (bcc: Albert Geven/EHV/RESEARCH/PHILIPS)
Subject: Re: OpenG Serial Port API
Classification:
Albert, how about allowing for both formats? The "9600,n,8,1" notation
is
something of a de facto standard, and is still in use. Doug
|---------+--------------------------------------------------->
| | alb...@ph... |
| | Sent by: |
| | ope...@li...ur|
| | ceforge.net |
| | |
| | |
| | 02/11/2005 11:29 AM |
| | Please respond to |
| | opengtoolkit-developers |
| | |
|---------+--------------------------------------------------->
>----------------------------------------------------------------------------------------------|
| |
| To: ope...@li... |
| cc: |
| Subject: Re: OpenG Serial Port API |
>----------------------------------------------------------------------------------------------|
Hi Martin
The most important reason that I do not use the old DOS parameter string
is
that I find it unreadable and you cannot extend it.
Readability is the one thing that keeps me laughing when looking at old
programs.
I send you the files as soon as I find them in my "archive"
Albert Geven Tel +31 (0)40 27
43019
Philips Research Fax +31 (0)84 722 9844
prof Holstlaan 4 WAA01 Email alb...@ph...
5656AA Eindhoven
To:
ope...@li...urcef
orge.net
cc: (bcc: Albert
Martin Henz Geven/EHV/RESEARCH/PHILIPS)
<mar...@mh...> Subject: Re: OpenG
Serial Port API
Sent by:
opengtoolkit-developers-admin@li Classification:
sts.sourceforge.net
11-02-2005 00:55
Please respond to
opengtoolkit-developers
Hi Albert,
alb...@ph... wrote:
> Good start Martin
hmm - not so good, because my e-mail should not go to the
mailing list ...
[...]
> Sometimes the instrument chokes on an inadvertently send hiccup on the
> line.
> It would be nice to inform the operating system of new "default values"
> before really initializing the port..
For the windows operating systems, these settings are in the
registry. I think, that it is only possible to change the
major parameters (baud rate, parity, stop bit and data bits)
using this way. It may be hard to examine that, because
different windows versions are sometimes using different
locations in the registry.
> I worked out a way to add these settings to a VISA resource name but did
> not yet inform the operating system.
> something like ASRL1::INSTR ;baudrate=9600;parity=even
Is there any reason, why you are not using the more default
notation like "9600,n,8,1"?
> In fact my application accepts the eventual hiccup after opening the
port
> because I did not have the time to sort out how to inform the OS.
Yes, it's much easier to change the settings if the serial
port is open. It may be also a starting point for the OpenG
serial port API.
> If you are interested I can send you the VI's but
> So even when using VISA for serial we need such a special serial open.
Yes, thank you - please send it to my e-mail address.
--
Martin Henz
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
OpenGToolkit-Developers mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers
This e-mail is intended solely for the person or entity to which it is
addressed and may contain confidential information. Any review,
dissemination, copying, printing or other use of this e-mail by persons or
entities other than the addressee is prohibited. If you have received this
e-mail in error, please contact the sender immediately and delete the
material from any computer.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
OpenGToolkit-Developers mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers
|
|
From: <Dou...@mk...> - 2005-02-11 16:39:41
|
Albert, how about allowing for both formats? The "9600,n,8,1" notation is something of a de facto standard, and is still in use. Doug |---------+---------------------------------------------------> | | alb...@ph... | | | Sent by: | | | ope...@li...ur| | | ceforge.net | | | | | | | | | 02/11/2005 11:29 AM | | | Please respond to | | | opengtoolkit-developers | | | | |---------+---------------------------------------------------> >----------------------------------------------------------------------------------------------| | | | To: ope...@li... | | cc: | | Subject: Re: OpenG Serial Port API | >----------------------------------------------------------------------------------------------| Hi Martin The most important reason that I do not use the old DOS parameter string is that I find it unreadable and you cannot extend it. Readability is the one thing that keeps me laughing when looking at old programs. I send you the files as soon as I find them in my "archive" Albert Geven Tel +31 (0)40 27 43019 Philips Research Fax +31 (0)84 722 9844 prof Holstlaan 4 WAA01 Email alb...@ph... 5656AA Eindhoven To: ope...@li...urcef orge.net cc: (bcc: Albert Martin Henz Geven/EHV/RESEARCH/PHILIPS) <mar...@mh...> Subject: Re: OpenG Serial Port API Sent by: opengtoolkit-developers-admin@li Classification: sts.sourceforge.net 11-02-2005 00:55 Please respond to opengtoolkit-developers Hi Albert, alb...@ph... wrote: > Good start Martin hmm - not so good, because my e-mail should not go to the mailing list ... [...] > Sometimes the instrument chokes on an inadvertently send hiccup on the > line. > It would be nice to inform the operating system of new "default values" > before really initializing the port.. For the windows operating systems, these settings are in the registry. I think, that it is only possible to change the major parameters (baud rate, parity, stop bit and data bits) using this way. It may be hard to examine that, because different windows versions are sometimes using different locations in the registry. > I worked out a way to add these settings to a VISA resource name but did > not yet inform the operating system. > something like ASRL1::INSTR ;baudrate=9600;parity=even Is there any reason, why you are not using the more default notation like "9600,n,8,1"? > In fact my application accepts the eventual hiccup after opening the port > because I did not have the time to sort out how to inform the OS. Yes, it's much easier to change the settings if the serial port is open. It may be also a starting point for the OpenG serial port API. > If you are interested I can send you the VI's but > So even when using VISA for serial we need such a special serial open. Yes, thank you - please send it to my e-mail address. -- Martin Henz ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ OpenGToolkit-Developers mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential information. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the material from any computer. |
|
From: <alb...@ph...> - 2005-02-11 16:31:22
|
Hi Martin
The most important reason that I do not use the old DOS parameter string
is that I find it unreadable and you cannot extend it.
Readability is the one thing that keeps me laughing when looking at old
programs.
I send you the files as soon as I find them in my "archive"
Albert Geven Tel +31 (0)40 27
43019
Philips Research Fax +31 (0)84 722 9844
prof Holstlaan 4 WAA01 Email alb...@ph...
5656AA Eindhoven
Martin Henz <mar...@mh...>
Sent by:
ope...@li...
11-02-2005 00:55
Please respond to opengtoolkit-developers
To: ope...@li...
cc: (bcc: Albert Geven/EHV/RESEARCH/PHILIPS)
Subject: Re: OpenG Serial Port API
Classification:
Hi Albert,
alb...@ph... wrote:
> Good start Martin
hmm - not so good, because my e-mail should not go to the
mailing list ...
[...]
> Sometimes the instrument chokes on an inadvertently send hiccup on the
> line.
> It would be nice to inform the operating system of new "default values"
> before really initializing the port..
For the windows operating systems, these settings are in the
registry. I think, that it is only possible to change the
major parameters (baud rate, parity, stop bit and data bits)
using this way. It may be hard to examine that, because
different windows versions are sometimes using different
locations in the registry.
> I worked out a way to add these settings to a VISA resource name but did
> not yet inform the operating system.
> something like ASRL1::INSTR ;baudrate=9600;parity=even
Is there any reason, why you are not using the more default
notation like "9600,n,8,1"?
> In fact my application accepts the eventual hiccup after opening the
port
> because I did not have the time to sort out how to inform the OS.
Yes, it's much easier to change the settings if the serial
port is open. It may be also a starting point for the OpenG
serial port API.
> If you are interested I can send you the VI's but
> So even when using VISA for serial we need such a special serial open.
Yes, thank you - please send it to my e-mail address.
--
Martin Henz
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
OpenGToolkit-Developers mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers
|
|
From: Jim K. <jim...@ja...> - 2005-02-11 16:04:25
|
Martin, This is a very good start. Attached is the same document you sent me, but after running a spell check (I rely heavily on spell check, too ;-) We should put this in the CVS repository. Have you been able to access the "serial" CVS module, yet? Skype me if you need assistance getting access. -Jim > -----Original Message----- > From: ope...@li... > [mailto:ope...@li...] > On Behalf Of Martin Henz > Sent: Thursday, February 10, 2005 6:23 AM > To: Jim Kring; ope...@li... > Subject: OpenG Serial Port API > > Hello Jim, > > I was a little bit off, but now the first description of the > project is available (see the attached lvserial.html). > Because my english is not the best, I would prever if you > are correcting this text. > > I've only set the font and font size inside the html file. > If you like to have more formatting elements I'll do that. > > -- > Martin Henz > > |
|
From: Martin H. <mar...@mh...> - 2005-02-10 23:57:10
|
Hi Albert, alb...@ph... wrote: > Good start Martin hmm - not so good, because my e-mail should not go to the mailing list ... [...] > Sometimes the instrument chokes on an inadvertently send hiccup on the > line. > It would be nice to inform the operating system of new "default values" > before really initializing the port.. For the windows operating systems, these settings are in the registry. I think, that it is only possible to change the major parameters (baud rate, parity, stop bit and data bits) using this way. It may be hard to examine that, because different windows versions are sometimes using different locations in the registry. > I worked out a way to add these settings to a VISA resource name but did > not yet inform the operating system. > something like ASRL1::INSTR ;baudrate=9600;parity=even Is there any reason, why you are not using the more default notation like "9600,n,8,1"? > In fact my application accepts the eventual hiccup after opening the port > because I did not have the time to sort out how to inform the OS. Yes, it's much easier to change the settings if the serial port is open. It may be also a starting point for the OpenG serial port API. > If you are interested I can send you the VI's but > So even when using VISA for serial we need such a special serial open. Yes, thank you - please send it to my e-mail address. -- Martin Henz |
4 messages has been excluded from this view by a project administrator.
