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
Copy file name to clipboardExpand all lines: README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ to the newest version, go to: *Tools* -> *Kotlin* -> *Configure Kotlin Plugin Up
30
30
# Features
31
31
32
32
## Inspections
33
-
LibGDXPlugin adds several inspections, which look for possible issues in a project. Code inspections support both Java and
33
+
libGDXPlugin adds several inspections, which look for possible issues in a project. Code inspections support both Java and
34
34
[Kotlin](https://kotlinlang.org/). To disable or enable inspections go to *Settings* -> *Editor* -> *Inspections* -> *libGDX*.
35
35
The following inspections are included:
36
36
@@ -54,7 +54,7 @@ The following inspections are included:
54
54
When using a libGDX color in Java or Kotlin code (e.g. `Color.BLUE` or `Color.valueOf("#0000ff")`) a preview of the the color is shown in the left gutter.
55
55
Color previews are also shown in the editor when editing Skin files and in the Debug Tool Window.
56
56
57
-
To disable color previews, go to *Settings* -> *Editor* -> *LibGDXPlugin*.
57
+
To disable color previews, go to *Settings* -> *Editor* -> *libGDXPlugin*.
58
58
59
59
## Skin JSON support
60
60
Files with the extension `.skin` are treated as Skin JSON files. For files with the extension `.json` which look like Skin files, you are asked
@@ -91,7 +91,7 @@ annotation (see below)
91
91
92
92
## JSON support
93
93
IntelliJ doesn't work well with libGDX-style JSON, which is more forgiving when it comes to things like unquoted strings and missing comma's.
94
-
LibGDXPlugin adds support for libGDX's custom JSON with the usual niceties of syntax coloring, completion, folding, etc.
94
+
libGDXPlugin adds support for libGDX's custom JSON with the usual niceties of syntax coloring, completion, folding, etc.
95
95
96
96
To have libGDXPlugin treat a JSON file as a libGDX-style JSON file: in the Project Window, open the context menu for the file
97
97
and select `Mark as libGDX style JSON`.
@@ -122,7 +122,7 @@ To get code completion, Go to Definition, Find Usages, Rename Refactoring, Diagn
122
122
* Region names from Atlas files in Skin.get*() and TextureAtlas.get*()
123
123
* Property keys in I18NBundle.get() and I18NBundle.format()
124
124
125
-
and related methods, use the `@GDXAssets` annotation to tell LibGDXPlugin which files to use.
125
+
and related methods, use the `@GDXAssets` annotation to tell libGDXPlugin which files to use.
126
126
127
127
First add the annotation to your build. In `build.gradle`:
128
128
@@ -197,7 +197,7 @@ Since version 1.9.9 libGDX skins support tagged classes: the ability to use shor
197
197
in Skin files. In addition to the standard, "built-in" short class names it is also possible to define custom
198
198
short names for your own classes by overriding `Skin.getJsonLoader()` and calling `Json.addClassTag()`.
199
199
200
-
LibGDXPlugin understands the default short names. It also tries to determine any custom short names by looking
200
+
libGDXPlugin understands the default short names. It also tries to determine any custom short names by looking
201
201
for calls to `addClassTag()`, but there is only so much it can do.
202
202
203
203
To explicitly tell the plugin to recognize one (or more) short names for one of your own classes, you can
0 commit comments