|
|
|
 "He who seeks originality will often find novelty, but not great design." - IKE [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools |
Rating: 
|
Display Modes |
|
|
|
| "He who seeks originality will often find novelty, but not great design." - IKE [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools |
Rating:
|
Display Modes |
|
#23
09-01-2011, 21:49
|
||||
|
||||
|
Re: RobotPy 2010.beta2
This is great!
I played with RobotPy a little, and here's a problem I encountered. When our code exits due to some error, it waits 5 seconds and then starts our script again, which is how we load new code. However, when it's an actual error, not an intentional interrupt for new code, while we look at the source and fix the problem it keeps on restarting every 5 seconds. Eventually it crashes with some memory error and we have to restart the robot. (I don't have the output in front of me; I'll try and reproduce it so I can post the exact error.) Has anyone else had this issue? How can I prevent it from doing this? 
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| RobotPy: Python for FRC | Peter Johnson | Python | 28 | 17-10-2012 11:46 |
| [FTC]: FTC 2010-2010 "A New Game" | JohnFogarty | FIRST Tech Challenge | 2 | 21-08-2010 22:34 |
| Connect a Million Minds 2010 Robotics Invitational, June 26, 2010 Columbus, Ohio | Dr. Osemwengie | Off-Season Events | 29 | 03-07-2010 00:33 |
| 2010 accelerometer | chsr | C/C++ | 1 | 22-01-2010 02:28 |
Threaded Mode