ed
3 years ago
1 changed files with 10 additions and 10 deletions
Split View
Diff Options
-
+10 -10BREAKING-CHANGES.txt
+ 10
- 10
BREAKING-CHANGES.txt
View File
| @@ -329,7 +329,7 @@ that the behaviour is the same. | |||
| Rationale | |||
| --------- | |||
| The ownership of this method is now clearer as the previous code relied on the | |||
| caller deleting the object. The name has changed to accomodate the new | |||
| caller deleting the object. The name has changed to accommodate the new | |||
| `Component::createFocusTraverser()` method that returns an object for | |||
| determining basic focus traversal, of which keyboard focus is generally a | |||
| subset. | |||
| @@ -442,8 +442,8 @@ Change | |||
| ------ | |||
| CharacterFunctions::readDoubleValue now returns values consistent with other | |||
| C++ number parsing libraries. Parsing values smaller than the minimum number | |||
| respresentable in a double will return (+/-)0.0 and parsing values larger than | |||
| the maximum number respresentable in a double will return (+/-)inf. | |||
| representable in a double will return (+/-)0.0 and parsing values larger than | |||
| the maximum number representable in a double will return (+/-)inf. | |||
| Possible Issues | |||
| --------------- | |||
| @@ -700,8 +700,8 @@ Limited. | |||
| Possible Issues | |||
| --------------- | |||
| Exising projects, particularly Android, may need to be resaved by the Projucer | |||
| and have the old build artifacts deleted before they will build. | |||
| Existing projects, particularly Android, may need to be resaved by the Projucer | |||
| and have the old build artefacts deleted before they will build. | |||
| Workaround | |||
| ---------- | |||
| @@ -755,7 +755,7 @@ Update the subproject path in the Projucer. | |||
| Rationale | |||
| --------- | |||
| Most other Xcode specific paths are specified reltive to the build directory. | |||
| Most other Xcode specific paths are specified relative to the build directory. | |||
| This change brings the Xcode subproject path in line with the rest of the | |||
| configuration. | |||
| @@ -1105,7 +1105,7 @@ Multiple changes to low-level, non-public JNI and Android APIs. | |||
| Possible Issues | |||
| --------------- | |||
| If you were using any non-public, low-level JNI macros, calling java code or | |||
| recieving JNI callbacks, then your code will probably no longer work. See the | |||
| receiving JNI callbacks, then your code will probably no longer work. See the | |||
| forum for further details. | |||
| Workaround | |||
| @@ -1134,7 +1134,7 @@ Rationale | |||
| --------- | |||
| Less than 0.5% of all devices in the world run versions of Android older than | |||
| Android 4.1. In the interest of keeping JUCE code clean and lean, we must | |||
| depricate support for very old Android versions from time to time. | |||
| deprecate support for very old Android versions from time to time. | |||
| Version 5.4.0 | |||
| @@ -1830,7 +1830,7 @@ or | |||
| Rationale | |||
| --------- | |||
| Previously, PopupMenus would not scale if the GUI of the target component (or | |||
| any of it’s parents) were scaled. The only way to scale PopupMenus was via the | |||
| any of its parents) were scaled. The only way to scale PopupMenus was via the | |||
| global scaling factor. This had several drawbacks as the global scaling factor | |||
| would scale everything. This was especially problematic in plug-in editors. | |||
| @@ -1935,7 +1935,7 @@ then you will need to update your plug-in to the new multi-bus API. Pre JUCE | |||
| 4.0.0 plug-ins are not affected apart from other breaking changes listed in | |||
| this document. | |||
| Woraround | |||
| Workaround | |||
| --------- | |||
| None. | |||