Subject:
|
Re: BricxCC release 3.3.2.12
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Thu, 29 Nov 2001 15:00:13 GMT
|
Viewed:
|
2681 times
|
| |
|
|
Hi John,
I haven't installed the new version yet.
Just a comment on my request. Your idea seems OK. However, this means you
need two read two files. If I would have a look into my old.nqc file two
months later I would see directly what settings where supposed to be used
(brick, com, etc..). With your idea I need to open as well the .sdk file....
Well, I agree, the easiest is for now better....:)
Coming to the problem below. Maybe you can "flag" the used com/USB port when
opening
a new session. When the asked port is in use, refuse to open a new session or
ask for closing the other one....
I will look into this Help window bug again....
Guido
In lugnet.robotics.rcx.nqc, Marco Correia writes:
> > From: news-gateway@lugnet.com On Behalf Of John Hansen
> >
> > 6. The feature request probably won't happen either. I might
> > add something
> > like the delphi "save desktop" feature that would save a file
> > with the same
> > name as the NQC file but with a different extension (DSK
> > maybe) that would
> > contain INI settings for brick type, port, program slot, and window
> > positions. That seems like it might be really easy to do.
> > When you open an
> > NQC file it would look for and open the corresponding DSK
> > file if it exists.
> > What do you all think about that?
>
> I think that's a reasonable approach.
>
> If I send a .nqc source file to someone using a CyberMaster connected to a
> diferent COM port, then this is a better solution.
> Also, by sending a .nqc that usually goes to Program 5 on my RCX, it won't
> accidentally destroy the Program 5 on my friend's RCX.
>
> On a multi pbBrick environment, with specific settings to that BricxCC
> instalation (CyberMaster on COM2, Scout on COM3 and RCX2 on USB) that will
> ease the opening of specific source files, while not interfering with
> someone else's setup, using a copy of the same .nqc files.
>
> Now, imagine this scenario:
> 1) Open a ex1cm.nqc file with a .dsk saying it's for a CyberMaster on COM2
> -> It will open a BricxCC session with that file and those settings
>
> 2) Then, open ex2rcx2.nqc file with a .dsk saying it's for a RCX2 on USB,
> Prg=4
> -> It will open *another* BricxCC instance with those settings, right ?
>
> 3) Open a ex3cm.nqc (.dsk for a CyberMaster on *COM3*)
> -> What happens ? Will the file be opened on the first BricxCC instance,
> because BricxCC finds no CyberMaster on COM3 and because there's already a
> BricxCC/CyberMaster instance running ?
>
> 4) Open a ex4rcx2.nqc (.dsk=RCX2,USB,Prg=3)
> -> The file will appear on the, already running, BricxCC/RCX2 session,
> right ?
>
> 5) Open ex5rcx2.nqc (.dsk=RCX2,COM3,Prg=3)
> -> What happens now ?
>
> 6) Open ex6rcx.nqc (.dsk=RCX,COM3,Prg=1)
> -> Will it try to find a RCX on COM3, reverting to the already running
> BricxCC/RCX2 instance if that fails ?
>
> As you can see, BricxCC should give priority on type of pbBrick when
> choosing (if possible!) between already running BricxCC instances.
>
> :)
>
> mc.
>
> PS: Thxs for BricxCC !
|
|
Message has 1 Reply:
 | | Re: BricxCC release 3.3.2.12
|
| (...) I guess I don't see so close a tie between the NQC code in a .NQC file and the brick type, port number, and program slot. A program running on RCX in slot 3 downloaded via COM4 could just as well run on an RCX2 in slot 1 downloaded via USB2. (...) (23 years ago, 29-Nov-01, to lugnet.robotics.rcx.nqc)
|
Message is in Reply To:
| | RE: BricxCC release 3.3.2.12
|
| (...) I think that's a reasonable approach. If I send a .nqc source file to someone using a CyberMaster connected to a diferent COM port, then this is a better solution. Also, by sending a .nqc that usually goes to Program 5 on my RCX, it won't (...) (23 years ago, 29-Nov-01, to lugnet.robotics.rcx.nqc)
|
5 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
