Quote:
|
Originally Posted by intelitek_Chris
Thank you for your suggestions. We are always interested in hearing constructive feedback about the software.
Chris G
|
Don't get us wrong. We think EasyC rocks! I don't think allot of people take it for a test drive then make a judgment too fast. Post I read on CD are really "sad to read".
It really is easy...mind blowing compared to all the hardship of interfacing we encountered last year trying to get our quad-encoders working and camera system. So far it seems flexible "enough" to do some pretty basic things, even PIDs. We don't feel at all limited. It makes coding tons faster, you don't have to remember your dumb variable names, or even mis-spelling them because if they aren't in the pull down list, then it's either not in the same scope "global/local" or we need to read the HELP file because we grabbed the wrong variable type to do that assignment. BTY, the help is awesome, kudos to the engineer that did the help files, love the videos inside the helps file and everything else about the help files. You guys did an awesome job with that.
more constructive...
One thing we like to do is "state" programming using Case Selects. Of course I don't see that in your command library. But, all we are going to do is track a state logic then do an If state = 1, then do this, If state = 2, then do this...pretty much the same as case selects...I dunno why people use case selects to do state logic, unless it complies smaller. But with 4X more memory who cares right??? knock on wood....
We also like to do our own PIDs. But our PID is nothing like a normal one, so it wouldn't matter if a PID function block as added to the default library or not. We will keep you posted if we get our PID wrote and converted into EasyC. Actually, we will probably post it in th FIRST Software Repository, later on in the season.
problems...
The only problem we've had is loosing the re-draw on the screen. I don't know if that is computer related or not at this point, but the graphics in EasyC seem to disappear onscreen. We have to shut it down and restart it to get the graphicals to reappear. It's like a chunk of it will be missing. I'll try and remember to do a screen shot the next time it happens.
Other than this, I'll let our programming team know about this post, and try to get the print-to-screen thing to behave. And we should be all set.