Also, if I click my cursor somewhere in the VS Code file, Pinegrow doesn’t follow suit (also vice versa).
In the Pinegrow extension settings in VS Code, I have set the url to http://127.0.0.1:40000 (the same as Pinegrow). (The original VS Code extension setting was http://localhost:40000). I have restarted both VS Code and Pinegrow but no luck.
Hey Don, I can confirm the same issue on Windows 11 even though it works as expected in macOS. Apparently Windows does some silly stuff (surprise!) that is making this difficult for live sync to work properly. Matjaz is aware of the issue and I sent him a video of it happening to me a day or two ago.
The issues with the VS Code extension come from url mapping between Pinegrow and VS Code on Windows. There, URLs are represented slightly differently and then the extension doesn’t recognize that the document is open in Pinegrow.
I just updated the VS Code extension to 0.0.9 with improved fuzzy logic for mapping urls, that should ignore slight differences in URL formatting.
Also, Settings now have the Enable debug checkbox that when enabled, outputs information to the debug console. We can use this for troubleshooting any issues. There was also a bug that caused endless “File was saved in the external editor” messages in Pinegrow when the document was saved in VS Code.
Please try to update the extension to 0.0.9 and let me know if it works better now. If it doesn’t work, enable the Debug mode:
@dculp@tytusie@kalsson1@vanheber I fixed some other issues in the last few days (thanks @adamslowe for testing it) and it appears to be working much better now. Please give the latest version 1.0.11 a try and let me know if it works.
@jonroc please provide debug information from v0.0.11, as described above in this topic.
Sorry about that. VS Code integration is an open issue that we are trying to improve, as evident from the many extension updates. The last update fixed the issue for many users. The debug info should help in troubleshooting your situation.