Skip to content
This repository has been archived by the owner on May 12, 2020. It is now read-only.

Particle Dev Autosave/Compile Problem #239

Open
robdobsn opened this issue Jan 26, 2018 · 3 comments
Open

Particle Dev Autosave/Compile Problem #239

robdobsn opened this issue Jan 26, 2018 · 3 comments

Comments

@robdobsn
Copy link

I have a problem using Particle Dev which is autosave on compile, while it does save changed files, doesn't result in the changes making it into the build.

I've recorded a video here showing the problem: https://youtu.be/iCqaO2leOX4

It looks like a race condition or similar. The video shows a project which has just been successfully built. Around 5s in I insert a syntax error (an "a" alone on a line) - and the blue dot appears to show dirty. I then press the build button (around 10s in) and the blue dot disappears and build begins. The build succeeds despite the error at around 20s in. I then remove the syntax error and build again (at 59s in) the build fails showing the error.

I checked if the file was really being saved when the build starts and it is. It just appears that the build is launched before the save has completed or similar.

So effectively the build is one save behind the current state.

@sprowt-labs
Copy link

I've been experiencing this same problem. I always need to compile twice to know if my changes will actually compile.

Any plans on addressing this issue?

@suda
Copy link
Contributor

suda commented Oct 4, 2018

Honestly, the last couple of months we have been focused on Particle Workbench so Particle Dev might not receive many updates/bugfixes now.
I encourage you to try out the Workbench though. It's still in preview but it's a worthy successor for Dev.

@robdobsn
Copy link
Author

robdobsn commented Oct 6, 2018

Completely nuts that you haven't fixed this before now. To me it looks like it should be a simple fix - it used to work - and it caused me to move to PlatformIO and that caused me to move away from Particle hardware as other things are better supported. Why launch another proprietary IDE now? Crazy in my opinion.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants