Subject:
|
Re: Another new RcxCC version
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Sun, 20 May 2001 22:45:36 GMT
|
Viewed:
|
2319 times
|
| |
|
|
hi John,
John Hansen wrote:
> In lugnet.robotics.rcx.nqc, Stef Mientki writes:
> > looks good, but I can't use it yet.
> > The main problem I have is that I can't see my templates. At once I found
> > them, a window 10 pixels win width and 25 pixels in height, and I can't
> > get it bigger. Am I doing something wrong ?
>
> I'm guessing the problem with templates is a registry problem. If you are
> comfortable with editing your registry you might check for a Templates key
> under HKEY_CURRENT_USER\Software\RcxCC\version 3.2\. If that key exists but
> it contains no string values then you will get a very tiny window like you
> describe. This probably happened because you ran RcxCC once when the files
> that are supposed to be in the Defaults directory were in the same directory
> as the EXE. It created the registry keys but put no values under them. Try
> running RcxCC /reset to reload the default values into the registry (or you
> can, alternatively, you can bring up the Template page in the Preferences
> dialog and click the Default button to reload just the template defaults).
RCXcc / reset
worked fine, that's a lot more extended then the orginal RCXcc !
>
>
> > My wishes (only 1 at the moment, and maybe difficult)
> > -------------------------------------------------
> > The "Tools"-menu, in a way like it's implemented in Delphi, but even somewhat more sophisticated.
> > Background I've written some programs to communicate with the RCX, to test
> > hardware and software I'd like to start these programs from within RCXcc.
> > So it's somewhat more complicated then the Tools-menu in Delphi,
> > because there must be some communication between RCXcc and the
> > other executables, because they share the same resources (comm-port).
>
> That's something I've been thinking about implementing. I can always close
> the com port before launching any user-defined "Tool". The way it is coded
> right now the next time I try to talk to the RCX it'll re-open the COM port
> if it isn't already open. I guess the tricky bit would be writing these
> other applications in a way that doesn't hold the COM port open continually
> or at least add a way to close the port from those other programs (and
> re-open it when needed).
At the moment I'm building such an implementation, the main program is a kind of oscilloscope and the launched application is a controler for a 8-channel multiplexed sensor. The idea I'm working out is the following, the main application is the master and all launched applications are slaves, so they have to ask the master to get control of the comport. After a slave gets the commport, the master always can ask the control back. Ok that's the weak part, the lauched programs must be programmed in
such a way that they react to the masters request, but if they don't ... the master still can kill the slave-process.
When I get it to work, I'll inform you.
>
>
> > When I first started the program, I got IO-error 103, my fault, I
> > dislike that winzip puts the files in his own directories and so
> > all the files came into one directory. Why not make a self-extracting
> > zip ?
>
> I'll eventually be creating a proper installer. But in the mean-time I
> agree it would be good to create a self-extracting zip EXE.
>
> > In the preferences I set "Don't connect to the brick" and on startup it
> > stills come with a message if it cann't make contact to the RCX.
>
> I think it works the same as the original RcxCC in this regard. But I'll
> check it out. It seems as if it would be fine to not display that message
> ever (as it is pretty obvious that some options are not available until you
> connect to the brick).
>
> > That terrible Toolbars !!, within 10 seconds you can move them in
> > such a way, that you can't find them anymore (it's a Delphi bug I
> > think). Why not fix them !
>
> I haven't had them be quite so problematic in my testing. But I agree they
> are far from perfect in their behavior. Maybe I'll make it possible to lock
> them from the preferences dialog.
What I forgot to mention, the toolbars restored themselfs after restarting the program.
What I also forgot to mention, on one of the machines I run Delphi, the toolbars of Delphi itself are rubish and I can't get them right anymore, you learn to live it ;-)
>
> > I you start fast polling ( watching the brick), the cursor is a
> > "waiting-glas", very unpleasant for clicking checkboxes or editing.
>
> I hadn't thought of that problem. I should definitely get rid of the
> hour-glass cursor I put in the poll code. Thanks for mentioning it! Thanks
> for all your suggestions/comments. And be sure to try the new graphing
> capability. :-)
I certainly will, but the next week I haven't time for my hobbies ;-(
>
> John Hansen
thanks for your reaction,
Stef Mientki
|
|
Message is in Reply To:
 | | Re: Another new RcxCC version
|
| (...) I'm guessing the problem with templates is a registry problem. If you are comfortable with editing your registry you might check for a Templates key under HKEY_CURRENT_USER\So...CC\version 3.2\. If that key exists but it contains no string (...) (23 years ago, 20-May-01, to lugnet.robotics.rcx.nqc)
|
4 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
