I am curious.
If the project works using MPLAB 8.x, why are you messing with MPLABX ?
I am curious.
If the project works using MPLAB 8.x, why are you messing with MPLABX ?
Dave
Always wear safety glasses while programming.
Good question. I'm starting to wonder. There are a lot of features in MPLABX that, after using it for a while, show MPLAB's age. The MPLABX editor is much better, version management is better, project handling (renaming, copying, moving, archiving) is better, workspaces are gone (yay!) in favor of projects, you can have multiple projects open at once (even using different compilers), etc. Plus Microchip won't be maintaining MPLAB any more.
But MPLABX is still pretty ragged. For all its promise, it's not ready for prime time yet. So to answer your question, I guess I'm trying to take it as far as I can to see if it's usable for me. I'm trying to get past issues such as the one in this post and then decide. Plus, if someone doesn't bring up these issues for examination, they might not be addressed by the MPLABX development team. The sooner the problem can be demonstrated in a repeatable manner, with as many clues as possible, the more likely the next version of MPLABX will have addressed them (that's assuming this particular issue is the fault of MPLABX, not Proteus or PBP).
I have not heard that. So you have heard that 8.86 is the last version? Darn, I hate NetBeans.Plus Microchip won't be maintaining MPLAB any more.
Dave
Always wear safety glasses while programming.
So they say. But there's widespread dislike of MPLABX (mostly because of its instability) so if they're smart they'll at least keep publicly supporting MPLAB for those whose business depends on it.
I can live with NetBeans if the IDE is stable. At the moment it's a real pain to use.
Bookmarks