-
-
Notifications
You must be signed in to change notification settings - Fork 21.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Highlight warning lines in Script editor #102469
base: master
Are you sure you want to change the base?
Conversation
I think it may be good (but not necessary) to have transparency check to skip code if alpha is zero. |
If the alpha is set to zero, warnings are added, then changed in the editor settings to something visible, it won't change until the next time warnings are updated. This is because it won't make the lines a color other than |
I understand you point.
Because users have errors if something is going wrong and usualy errors should be fixed. But there could by many warnings and they could be freely ignored. This is just a suggestion (I'll rephrase previous comment) and not critical at the first glance. |
Checking for alpha would allow skipping double for loop. If setting the background color would have no effect, no reason to run this loop. Same could be done for errors. |
Done for warnings and errors both, I also added the missing documentation that was causing the Linux mono build to fail I think |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested locally, it works as expected.
However, I think the default warning mark is too prominent by default and draws attention away from errors.
Default | Black (OLED) | Light |
---|---|---|
![]() |
![]() |
![]() |
With opacity reduced by half on the warning mark color:
Default | Black (OLED) | Light |
---|---|---|
![]() |
![]() |
![]() |
We should remember that many projects out there have dozens of warnings (if not hundreds) that were never noticed by users (and therefore not fixed), so we should ensure we don't highlight warnings too prominentl by default.
Looks good to me, please squash the commits together. See PR workflow for instructions 🙂 |
a1de881
to
4472bce
Compare
Commits are now squashed together |
4472bce
to
d7916d9
Compare
d7916d9
to
eb99adb
Compare
Adds a yellow highlight (customizable through the theme editor) to the script editor
![image](https://private-user-images.githubusercontent.com/106356149/410219773-17c83278-1d3d-476d-9c8e-c00977931ce1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk0Njk1NDEsIm5iZiI6MTczOTQ2OTI0MSwicGF0aCI6Ii8xMDYzNTYxNDkvNDEwMjE5NzczLTE3YzgzMjc4LTFkM2QtNDc2ZC05YzhlLWMwMDk3NzkzMWNlMS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjEzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxM1QxNzU0MDFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT05ODA4NWFkYWM1YzZkNjhkOTM0MmVmMjlkZmEyMzg4MzEwNzYwN2RmMzY1NWIwOGY3Njk3ZTI5YTIwNGQwMmFlJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.Wo2viGS5esJeG6q9UtpqjjAYkq0l1is66RxxzRKxa-U)
Resolves godotengine/godot-proposals#11706