You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 18, 2024. It is now read-only.
Writing in the Android IDE, I noticed some color inconsistencies when I do certain things in my code, here are the main mistakes I noticed
1- Referencing an activity in a context turns its color white as you can see in the images below
2 - Put variable and private variables as parameter of classes, data classes makes that contents of the parentheses blue, if i remove the leading parenthesis it seems to go back to normal colors but that would not compile
3- Annotations color should be yellow in my opinion not only because it matches Android Studio, but because in certain cases it would differ from the color of other elements that are already blue too as in this example where the class name is already blue and the annotation parameter which is also blue this would make it more readable
for color comparison
I think these are the main points
What's the expected behavior?
Colors do not suffer from these inconsistencies when writing code and make the code more beautiful visualization
What version of AndroidIDE you're using?
v2.4.0 (debug builds)
Relevant log output
No response
Duplicate issues
This issue has not been reported yet.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
* fix: parse OpenedFilesCache manually to avoid ClassCastException in release builds (fixesAndroidIDEOfficial#1102)
* chore(workflow): maven central credentials not provided to 'publish' job
* chore(workflow): run 'publish_snapshots' job on branches other than 'main'
* chore: fix apk file path in Nyx config
* build: fix project description missing in modules that are published
* fix: close tree sitter language instance when editor language is destroyed
* build: require project description for modules that are published to maven central
* docs: update links in README
* docs: update README
* fix(editor): update syntax highlights for Java and Kotlin (fixesAndroidIDEOfficial#1051)
* chore: update version numbers in issue templates
* fix: simplify logic for determining forward/backward transition in main activity
* fix(editor): invalid syntax highlights for annotations in Java
* fix(editor): fall back to default color scheme if custom scheme doesn't support a file type
* Update gradlew
---------
Co-authored-by: Akash Yadav <itsaky01@gmail.com>
I'll have to modify the grammar for this which could take some time. This is because that statement can have a qualified reference as well. For example :
What happened?
Writing in the Android IDE, I noticed some color inconsistencies when I do certain things in my code, here are the main mistakes I noticed
1- Referencing an activity in a context turns its color white as you can see in the images below
2 - Put variable and private variables as parameter of classes, data classes makes that contents of the parentheses blue, if i remove the leading parenthesis it seems to go back to normal colors but that would not compile
3- Annotations color should be yellow in my opinion not only because it matches Android Studio, but because in certain cases it would differ from the color of other elements that are already blue too as in this example where the class name is already blue and the annotation parameter which is also blue this would make it more readable
for color comparison

I think these are the main points
What's the expected behavior?
Colors do not suffer from these inconsistencies when writing code and make the code more beautiful visualization
What version of AndroidIDE you're using?
v2.4.0 (debug builds)
Relevant log output
No response
Duplicate issues
Code of Conduct
The text was updated successfully, but these errors were encountered: