Subject:
|
BricxCC release 3.3.3.2
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Sat, 5 Jan 2002 23:21:17 GMT
|
Viewed:
|
652 times
|
| |
|
|
I've just uploaded another release of BricxCC.
Version 3.3.3.2 fixes a few bugs in the toolbar button/menu item
enabling/disabling dependant on whether the connection to the programmable
brick is active or not.
It implements auto saving of the "desktop" file which stores window
positions and connection/program slot information to a ".dsk" file
associated with the ".nqc" file. On opening a file that has an associated
desktop file the program will restore the settings contained in the desktop
file.
This release adds a couple new buttons to the Tools toolbar
(if your Tools toolbar sizes oddly after upgrading to this release
try floating the toolbar, resize it sufficiently wide to fit all the buttons
on one line, then dock it again).
It adds the ability to save the NQC compiler output (as a ".rcx" file).
(This is a step toward adding a feature that lets you "open" a ".rcx" file
which will simply download the already compiled program via NQC to the
current port, brick type, and program slot.)
It adds a configuration setting on the "Start Up" tab of the preferences
dialog to specify whether to always display the "Find Brick" dialog when you
execute the "Find Brick" option. (If you don't want to always be prompted
when you choose Find Brick then you can turn this setting off.)
It moves the "View/Toolbars" sub-menu to a right-click popup menu
on the top toolbar dock site.
The error message displayed when BricxCC cannot find NQC is improved.
Several users experienced difficulty with not having NQC installed
correctly. The revised error message should make this much clearer. The
BricxCC.htm file on my website has also been updated to help clarify this
issue as well as to more completely describe a simple installation process.
BricxCC now reopens the port after it finishes running NQC. In the previous
release certain options would become disabled after a compilation because
BricxCC used to close the port and not re-open it until the user selected an
option that would cause the port to automatically re-open. In earlier
releases several options were (incorrectly) left enabled even though the
port was no longer open.
An option to display source information in the compiler code listing has
been added.
Let me know what you think.
John Hansen
http://members.aol.com/johnbinder/bricxcc.htm
|
|
1 Message in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
