Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 3.1
edited by stefan
on 2019/02/01 02:11
Change comment: added initial version
To version 5.1
edited by stefan
on 2019/02/01 02:33
Change comment: added SetFormationShape() case

Summary

Details

Page properties
Content
... ... @@ -15,7 +15,7 @@
15 15  
16 16  
17 17  
18 -Please note that issues introduced during the beta phase might not be explicitly mentioned as a breaking change, if things would only be broken in-between two beta versions. While we still aim to document any (potential) breaking change here, there might be circumstances for which we divert from that procedure (especially in case of minor issues introduced only in-between beta releases).
18 +Please note that issues introduced during the beta phase might not be explicitly mentioned as a breaking change, if things would only be broken in-between two beta versions. While we still aim to document any (potential) breaking change here, there might be circumstances for which we divert from that procedure (especially in case of minor issues which is considered merely a bugfix than an intended behavior change).
19 19  
20 20  = Breaking Changes =
21 21  
... ... @@ -38,9 +38,14 @@
38 38  //Before 2.0 Beta 1 using GetUpgradeSlotCurrentComponent() only performed on operational objects (i.e. not wrecked objects or objects under construction). Since this is inconsistent with the rest of the UI functions, this was considered a bug and fixed in 2.0 Beta 1. If you require the old behavior, use the FFI function: IsComponentOperational() to check the passed object's state before making the call.//
39 39  )))
40 40  |(((
41 -
41 +UI extensions
42 42  )))|(((
43 -
43 +2.0 Beta 1
44 44  )))|(((
45 -
45 +SetFormationShape() no longer indicates an error upon certain error cases
46 46  )))
47 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
48 +(((
49 +//Before 2.0 Beta 1 a call to SetFormationShape() indicated an error state to the caller in certain cases where setting a formation shape (potentially) failed. Due to a design flaw in the handling of formations, this however doesn't do any good, since the function by itself doesn't really set the formation shape in all cases. On top of that the call can fail at random. Hence, at the moment an indication of an error case that setting a formation potentially fails is no good to the caller and he has no means to distinguish that case from a real error case.//
50 +//Therefore, in 2.0 Beta 1 we drop the error indication in case of an attempt to set the formation fails. We are currently working on a better solution to the underlying problem and hope to have it ready as part of a following beta.//
51 +)))
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -78577861
1 +78577865
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/78577861/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/78577865/Breaking Changes