![]() |
Eclipse is being a butt
Hello, it is I, Lord Supreme Programmer with Team 1410, and I am trying to write the code for the bot this year, but alas, I keep getting these errors while using CANTalon:
The type 'CANTalon' must implement the inherited pure virtual method 'CANSpeedController::ConfigPotentiometerTurns' and so on. It says this for every CANTalon I write, and nothing seems to go away. The file still works and builds, but these errors are annoying. Does anyone know how to fix this? |
Re: Eclipse is being a butt
Lord Supreme Programmer, try to rebuild in the index.
http://wpilib.screenstepslive.com/s/...p-test-program |
Re: Eclipse is being a butt
Quote:
Rebuild project clean and rebuild rebuild index un/reinstall libraries un/reinstall toolchain un/reinstall eclipse rewritten entire project restarted computer xMany times I just can't fix it. My mentor had the same problem, but after a minute it disappeared |
Re: Eclipse is being a butt
Quote:
|
Re: Eclipse is being a butt
That's a bummer usually re-indexing fixes it, but I still think it's syntax parser related only because you said the project still builds, and I know for a fact ConfigPotentiometerTurns is implemented (it's an empty implementation).
Just to sanity check (I'm sure you did this too) but maybe it might help another team having similar symptoms.... -navigate to the Problems tab and manually delete all the errors and warnings. You can highlight the treenodes in there and press delete or right-click-menu-delete. Eclipse will warn about deleting the error being permanent, hit ok. Then in the project explorer, under binaries delete your FRCUserProgram. This step is necessary just for checking that the project does build. Close all other open projects in eclipse except for the one you care about. Clean the project. (takes a min, while you wait the build menu item will be gray) Full build (or CNTRL+B), and let it finish. Confirm FRCUserProgram is back (because it built ok). Confirm if you still get the parser errors. |
Re: Eclipse is being a butt
Quote:
fl_motor = new CANTalon(1); I think eclipse is just trying to make me go crazy. |
Re: Eclipse is being a butt
Quote:
(I'm wondering what happened to the front_left_drive constant that used to be where the 1 is now, but that's not really important right now.) Quote:
|
Re: Eclipse is being a butt
Quote:
I have that line in the subsystem DriveBase. Chief Delphi won't let me upload the file again, as I already have it here: http://www.chiefdelphi.com/forums/sh...6&postcount=15 but its the same file. |
Re: Eclipse is being a butt
Yeah so one thing that's unique about eclipse is the error/warnings sometimes tend to stick around even after you resolve and rebuild. I'm guessing that was the first problem.
That new error sounds like a genuine compiler error, so that means the linker isn't able to create FRCUserProgram. Probably should confirm that though. That also means that you haven't actually been successfully building this whole time, which is good to know. That line with the Talon c'tor error probably has been a problem this whole time and now it's revealing itself. Maybe make a simple project first and merge in your stuff in pieces until the error shows up to see what the cause is. Alan's right, the problem is likely before that line, could be in one of the headers too. |
Re: Eclipse is being a butt
Quote:
|
Re: Eclipse is being a butt
1 Attachment(s)
Quote:
|
Re: Eclipse is being a butt
int GetNumberOfQuadIdxRises();
void SetNumberOfQuadIdxRises(int rises); virtual bool GetForwardLimitOK() override; virtual bool GetReverseLimitOK() override; virtual uint16_t GetFaults() override; uint16_t GetStickyFaults(); void ClearStickyFaults(); ...maybe you bumped spacebar or something while navigating/viewing the headers? |
Re: Eclipse is being a butt
Quote:
I just added it in and the program finally built without any errors, thanks for all the help. I will go and make sure that all my under-programmers fix that error, too, as they all copied their installation of Eclipse from me. Maybe finally all of our code will build perfectly. I still stand by Eclipse isn't the best, and I still hold out hope that Microsoft will swoop in and save the day by helping to make Visual Studio available as a dev tool for FRC, but now that everything is working I'm content with Eclipse for now. |
Re: Eclipse is being a butt
Quote:
|
Re: Eclipse is being a butt
Quote:
|
Re: Eclipse is being a butt
Quote:
|
Re: Eclipse is being a butt
Quote:
|
Re: Eclipse is being a butt
Quote:
Neither Wind River, FIRST, Eclipse or FSF had anything to do with mangling your headers. Someone probably accidentally deleted the method name - happens to everyone now and then. Visual Studio is not (though it can be painfully modified) by default for cross development. Using Eclipse under Linux for cross development is the choice for many professionals. Personally I would not touch Visual Studio with a ten foot pole - every other version is way too buggy and I don't write PC apps. |
Re: Eclipse is being a butt
Quote:
double speed = 0.5; and got and error that said (not exact quote) "incompatible types, int to double" My point is, Eclipse hasn't been stable at all for me, and I would rather have a tool I know works and trust (Visual Studio) than a tool that has not worked so far. I can't even import a project into a workspace, for crying out loud! |
Re: Eclipse is being a butt
Quote:
|
Re: Eclipse is being a butt
Quote:
|
Re: Eclipse is being a butt
Quote:
|
Re: Eclipse is being a butt
Quote:
|
Re: Eclipse is being a butt
Quote:
|
Re: Eclipse is being a butt
Quote:
|
Re: Eclipse is being a butt
I've seen your posts in several forums and there is a definite (and worrisome) theme. You are having troubles that few others experience (as in zero) and coming up with solutions that don't make much sense whilst disregarding advice from some very sharp engineers. Perhaps it is time to be honest with yourself and your team and get some help from a local mentor. We have 4 students (2 new to FRC) and myself using Eclipse/C++ and a custom software design and are having no problems. I can see your team getting to your first competition and failing miserably when running wireless hooked up to the field. And then it is too late - be humble, get some help while you still can.
|
| All times are GMT -5. The time now is 13:11. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi