Author | Topic: Breaking changes | |
---|---|---|
S++awomir Ciupinski | Breaking changes on Sat, 15 Nov 2014 21:39:15 +0100 We have encountered multiple breaking chnges when trying to migrate solution from 1.9 to 2.0 Is there any list of braking changes in behavior or migration guidlines that everybody can use when migrating to 2.0? I will give some examples to warn others... 1. XbpComboBox:itemSelected - only raised when selected with mouse. Currently there is no suitable event for selecting an item with the keyboard. If you "select item" with up down keys on combo box the event is not raised. That forced us to workaround. 2. Multiple painting differences due to changed order or behavior. (Currently have no example for that) 3. XbpBrowse:navigationmode does not change only the behavior of scrolling. In our solution we are creating the XbpSLE when user enters cell, and focus into XbpSLE (which enables us to do inline table editing). The solution from XBase 1.9 does not work in XBase 2.0 when navigationMode is set. (Probably changed order in SetFocus, KillFocus) 4. Others not listed. | |
Andreas Herdt | Re: Breaking changes on Mon, 17 Nov 2014 16:05:33 +0100 Hello Mr Ciupinski, We take great care and invest much to provide backward compatibility with each individual release. Hence, if behaviour changes then we need to understand what is happening. This is precondition before we can qualify each individual issue and before being able to provide a fix. With the update capabilities we have a way to release fixes in a timely reasonable fassion, we have to understand the issue, anyway. First: What versions are you comparing. What is the build number of the earlier 1.9 installation - what Hotfixes have been installed. Secondly, please make available a sample for each individual issue you are reporting. This is especially important for the third one because a somehow complex scenario seems to be affected. Create distinct threads on this newsgroup for each individual issue. With my best regards, Andreas Herdt Alaska Software -------------------------------------------------------------------- Technical Support: support@alaska-software.com News Server: news.alaska-software.com Homepage: http://www.alaska-software.com WebKnowledgeBase: http://www.alaska-software.com/kbase.shtm Fax European Office: +49 (0) 61 96 - 77 99 99 23 Fax US Office: +1 (646) 218 1281 -------------------------------------------------------------------- "S++awomir Ciupinski" wrote in message news:179c1380$646e6d9d$1061c2@news.alaska-software.com... > We have encountered multiple breaking chnges when trying to migrate > solution from 1.9 to 2.0 > > Is there any list of braking changes in behavior or migration guidlines > that everybody can use when migrating to 2.0? > > I will give some examples to warn others... > > 1. > XbpComboBox:itemSelected - only raised when selected with mouse. Currently > there is no suitable event for selecting an item with the keyboard. If you > "select item" with up down keys on combo box the event is not raised. That > forced us to workaround. > > 2. > Multiple painting differences due to changed order or behavior. (Currently > have no example for that) > > 3. > XbpBrowse:navigationmode does not change only the behavior of scrolling. > In our solution we are creating the XbpSLE when user enters cell, and > focus into XbpSLE (which enables us to do inline table editing). > The solution from XBase 1.9 does not work in XBase 2.0 when navigationMode > is set. (Probably changed order in SetFocus, KillFocus) > > 4. > Others not listed. |