I hate that environment; renaming one of these didn’t help!
And each even private upload needs a new version to take effect.
That should only be true once you have published a version. As long that version number wasn't made public you can re-upload as often you want.
I think it is needed if files need be removed. Else only files update or add is done. At least it looked so on my initial updates.
I have put GxEPD2_PP on GitHub, for anyone who can help with this issue.
clear browser data on exit, helped with the non-terminating Loading… issue.
At least it looks like, as I could again load the libraries, a few times per session.
I need to find out what to clear instead of all, as having to log in every time is a bit a nuisance.
GxEPD2_PP is published now. For support use the Arduino Forum Display topics linked in README.MD.
3 Likes
If I read though this whole topic once more, I see many questions that have never been answered, e.g. the original one.
Anyway, the help I got is highly appreciated! Thank you all.
Which would that be? If you can quote it that would help.
The first post rather seems to be stating some issue than asking a question.
Yes, you are right, I didn't formulate it as a question. I think it is an issue. I expected a confirmation, or an explanation what I might have done wrong.
And yes, I got an answer, to avoid to use Particle Desktop IDE.
And yes, I got an answer about the Particle Build WEB-IDE, that it will be ditched.
So this leaves only the Particle CLI for practical use for a developer.
I fully understand that developers only use Particle CLI, but when developers don't use the other tools, then these tools may not reach a state that is really usable for users.
This is my personal view. And I would like to express my gratitude to have tools for use with Particle devices.
No quite, it should be replaced with a better - but still web based - solution that ties in a bit closer with VS Code (on which Particle Workbench is based) and GitHub to provide a more uniform UX.
Nope, Particle Workbench should be the IDE of anybody's choice for dev, CLI should rather be seen as a maintenance tool which just happens to also provide dev features.
So to wrap it up, Particle Dev and Web IDE were a good start at the time, but as development has moved on better tools emerged (or are in the process of) and hence will supersede the old tools which will eventually be deprecated.
1 Like
I don't know why the fixed one didn't build in Desktop IDE for me. Now I fixed it and it works.
And I verified now that the structure works with Desktop IDE with my example https://github.com/ZinggJM/PxEPD2/tree/master/examples/PxEPD2_Example.
There are some possible reasons, but the Desktop IDE isn’t very forthcoming with usable error messages.
If your project contains multiple .ino files (even in subdirectories - e.g. lib/examples) or when your project.properties file contains dependencies to libraries that are also available in the lib folder.
1 Like
I think this was the reason. I didn't know if a local library should be in the project.properties dependency.
This also explains why the error went away for an other test after I uploaded the library.
After having used particle compile proton and seen the output, I better understand what dependency does.
1 Like