How simple should commands be? And how should they be structured?

I hope you realize that by starting this thread you have earned yourself a permanent place at the "WOEWITWISTFT" ("What On Earth Was I Thinking When I Started THAT FIRST Trend?") table. It's members are few, but the conversation is the most honest and amusing in the entire place. ;) - Jessica Boucher [more]

		Chief Delphi > Technical > Programming
How simple should commands be? And how should they be structured?

Thread Tools

Rate Thread

Display Modes

29-04-2016, 16:48

GeeTwo

Technical Director

AKA: Gus Michel II

FRC #3946 (Tiger Robotics)

Team Role: Mentor

Join Date: Jan 2014

Rookie Year: 2013

Location: Slidell, LA

Posts: 3,679

Re: How simple should commands be? And how should they be structured?

As far as I am aware, none of our commands take arguments.

As an example, for our ball pickup, we have four separate commands:

BallPickupForward()
BallPickupReverse()
BallPickupStop()
ControlIntakeMotor()

ControlIntakeMotor() reads the joystick and selects the appropriate command of the other three. (It would probably have been better named something like BallPickupOperate()).

__________________

If you can't find time to do it right, how are you going to find time to do it over?
If you don't pass it on, it never happened.
Robots are great, but inspiration is the reason we're here.
Friends don't let friends use master links.

Last edited by GeeTwo : 29-04-2016 at 16:50.

« Previous Thread | Portal | Next Thread »

Thread Tools
Show Printable Version Email this Page
Display Modes	Rate This Thread
Switch to Linear Mode Switch to Hybrid Mode Threaded Mode	Rate This Thread:

Posting Rules
You may not post new threads You may not post replies You may not post attachments You may not edit your posts vB code is On Smilies are On [IMG] code is On HTML code is Off

Forum Jump

All times are GMT -5. The time now is 19:15.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.