| | Re: BricxCC Feedback Requested
|
|
(...) There are no functional differences between the planned toolbars and menus aside from the toolbar docking support. The difference is really just in appearance. I have spent the last several months in my real job working on a project to spruce (...) (19 years ago, 16-Apr-06, to lugnet.robotics.rcx.nqc, FTX)
|
|
| | Re: BricxCC Feedback Requested
|
|
(...) John, As other's have elluded to, I am not worried about changes to the IDE environment... I am hooked on this tool, so whatever you come up with, I will work with it.. Dave (19 years ago, 16-Apr-06, to lugnet.robotics.rcx.nqc, FTX)
|
|
| | Re: BricxCC Feedback Requested
|
|
(...) Me too- what he said, all of it. Mindstorms wouldn't be 1/16 as cool without BricxCC. But I just use it, I don't move stuff around. Tim (Smith) (19 years ago, 16-Apr-06, to lugnet.robotics.rcx.nqc, FTX)
|
|
| | Re: BricxCC Feedback Requested
|
|
(...) Nope. I leave stuff where it is. (...) Nope. I leave stuff where it is. (...) The whole BricxCC environment is the single most important feature making Mindstorms inherently usable for me. Thanks John, for all the work you've put into its (...) (19 years ago, 16-Apr-06, to lugnet.robotics.rcx.nqc, FTX)
|
|
| | Re: BricxCC Feedback Requested
|
|
(...) I never use this. (...) Don't use it. Wouldn't miss it. (...) In any event, I really like BricxCC. Thank you for giving me something easy with which to program my RCXs! (19 years ago, 16-Apr-06, to lugnet.robotics.rcx.nqc)
|
|
| | Re: BricxCC Feedback Requested
|
|
(...) No - I never use it. (...) Well I have used that to arrange the toolbars how I prefer, but I've no doubt I could get used to a different configuration fairly quickly, so no major objections there. (...) Well I don't use outlook, so I don't (...) (19 years ago, 15-Apr-06, to lugnet.robotics.rcx.nqc, FTX)
|
|
| | BricxCC Feedback Requested
|
|
I am revising the BricxCC GUI a bit and I would like to get some input from users. Do you care about docking toolbars to the left, right, or bottom of the BricxCC main window? In other words, would it bother you if that feature was removed? What (...) (19 years ago, 15-Apr-06, to lugnet.robotics.rcx.nqc, FTX)
|
|
| | NQC/MacNQC running on MacBookPro (intel) with a serial tower ?
|
|
Hello, I currently own two Mindstorms 2.0 sets. I'm wondering buying a SERIAL/USB adapter for connecting a Serial IR Tower to a MacBook Pro (intel processor) under MacOS X. Do you think NQC/MacNQC will work fine, detect the IR Tower and the RCX, (...) (19 years ago, 5-Apr-06, to lugnet.robotics.rcx.nqc)
|
|
| | Re: NQC and NXT
|
|
...This is possibly even better news than the creation of the new brick itself. Many thanks! (19 years ago, 10-Jan-06, to lugnet.robotics.rcx.nqc)
|
|
| | Re: NQC and NXT
|
|
(...) and found NQC. I never looked back. It is great that you volunteered to take over NQC, when Dave retired. The community is much better off because of your efforts on NQC and BricxCC). Thanks, Kev (19 years ago, 9-Jan-06, to lugnet.robotics.rcx.nqc)
|
|
| | Re: NQC and NXT
|
|
(...) Sounds great! So far, I was missing any positive statement concerning the compatibility of NXT and RCX. Now, with NQC, we will have certain compatibility with respect to the software. Compared to this the different hardware will be of (...) (19 years ago, 9-Jan-06, to lugnet.robotics.rcx.nqc)
|
|
| | Re: NQC and NXT
|
|
(...) Excellent! NQC has been my language of choice, largely because of such community support. Thank you John (and, originally, Dave, and others for providing me with aMac GUI, and... well, this is why I said "community") for this support. (19 years ago, 9-Jan-06, to lugnet.robotics.rcx.nqc)
|
|
| | Re: NQC and NXT
|
|
(...) created. This with NQC (thx Dave B) have enabled me to expand the possibilities of my bots. I look forward to hearing more about it! Dave (19 years ago, 9-Jan-06, to lugnet.robotics.rcx.nqc)
|
|
| | Re: NQC and NXT
|
|
(...) That's excellent John, if I had any knowledge in that area I'd offer you some help, but alas... Thanks for your great tools! (and Dave B for originally creating NQC). ROSCO (19 years ago, 9-Jan-06, to lugnet.robotics.rcx.nqc)
|
|
| | NQC and NXT
|
|
In case anyone is interested, I have been keeping up as best as I can with the news about the new LEGO brick. As soon as I get my hands on one (or sooner, if possible) I will begin the process of adding support for this new brick to NQC. The same (...) (19 years ago, 9-Jan-06, to lugnet.robotics.rcx.nqc)
|
|
| | Re: Memory question
|
|
(...) So what your saying is I should split my program into more functions not less, so that the local ints are destroyed and available for re-use. That's a great idea, it's the complete opposite of my question but fulfills my goal perfectly :-). (...) (19 years ago, 13-Dec-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: Memory question
|
|
(...) Most functions in NQC are in-line functions, so in a sense they probably *are* in main(). One thing I do is place all my initalization code (as much as possible) into inline functions. That way, when the compilier runs through, it can allocate (...) (19 years ago, 13-Dec-05, to lugnet.robotics.rcx.nqc)
|
|
| | Memory question
|
|
Say I had a program that has a very large block of start-up/calibration code that is run once at the top of the program. Does it make any difference if I keep it in the "Main()" task, or put it in a function? I mean from the point of stack space (...) (19 years ago, 13-Dec-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: Help me convert this train program to use events (NQC)
|
|
(...) (URL) (...) I bought some alligator clips to use with some 24-guage wire. I'll become impure just this once, but I won't resort to willful LEGO destruction. :) (19 years ago, 1-Dec-05, to lugnet.robotics.rcx.nqc, FTX)
|
|
| | Re: Help me convert this train program to use events (NQC)
|
|
(...) If it were me, I'd destroy one small LEGO 9v wire. Cut the wire in half, and splice in a long segment of speaker wire. That would look better than a short layout, or the battery-powered train. Steve (19 years ago, 30-Nov-05, to lugnet.robotics.rcx.nqc)
|