Dexter Posted Friday at 06:22 PM Posted Friday at 06:22 PM I chased a ghost for a bit before realizing the integrated editor doesn't detect external edits. I was editing in vscode, modifying a map, saving and running the old script in LE while external editors on the other side will usually make it obvious , LEs in-memory buffer remains unchanged and it can be confusing. maybe a warning & reload/option would be good! Relatedly, debug output only goes to the editor output when running from the editor w/o a console window present. it would be nice to have it go to the main output window when the script editor is closed, or an option. It wasnt immediately clear to me where the output was going when ran from directly from LE with the script editor closed. Not a big deal tho when running from vscode debug proper though 1 Quote
Josh Posted Friday at 10:23 PM Posted Friday at 10:23 PM Were you modifying a map file or a script file? Quote My job is to make tools you love, with the features you want, and performance you can't live without.
Dexter Posted yesterday at 03:52 AM Author Posted yesterday at 03:52 AM to clarify, the problem is with script editor ui (f3) only, eg: 1. open script editor and MyCoolComponent.lua in LE editor 2. switch/open vscode and edit MyCoolComponent.lua in vscode, save 2. tab back to editor, edit a map or whatever you were doing, switch back to code editor 3. code editor is showing code outdated from 2. edits, edit old code, save, overwriting external edits 4. run and wonder why wtf was just working seemd to break again lol again, not a huge deal if you just stick to what you're doing in an external editor, but i kinda footgunned for a minute 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.