Last week Xojo 2019 Release 3.1 hit the internet. This small bug fix release is a critical update and is recommended if you are using one of several areas. Let’s get into the details.
One of my biggest issues of concern with API 2.0 is with a dangerous memory leak in the DatabaseRow class. Doing practically anything with a database would quickly eat of RAM until it brought your machine to its knees. R3.1 fixes this issue and also a memory leak when using ODBC.
A couple of iOS bug were fixed in this release. R3.1 fixes a regression that caused iOSTextAreas to overflow their bounds when the border was set to None or Regular. iOSView headers no longer show the previous view during the PushTo animation. Xojo added the Operator_Compare to the ColorGroup so that it can be compared against a color value.
A number of API 2.0 bugs (besides the database bugs noted above were fixed):
- TextArea.SelectionAlignment now accepts enum values.
- String.IndexOf now properly matches its signature when you leave off the startPosition but include ComparisonOptions or Locale.
- If an empty name is used in the TimeZone constructor it will create an instance for the current timezone.
- String.LastField now works
- SerialConnection.Connect no longer raises an Error event. It now throws an exception as expected.
- DateTime no longer reports a Nil TimeZone
In Windows, having multiple HTMLViewers on a window (or multiple windows) no longer continuously switches focus.
In MacOS setting FolderItem.Visible no longer inverts the visibility.
The Plugin SDK now lets you access the new API 2.0 string extension methods.
The burning question that everyone wants to know: Do I think that Release 3.1 is safe to use? The answer is a definite maybe. Let me explain.
I’m still not sold on API 2.0 being completely stable. A few additional bug reports were filed after R3.1 was released including a GenerateJSON bug with Variant arrays (Feedback 58940), and a DatabaseColumn.Value bug where value always returns a String value (Feedback 58934) where it should be bringing back the correct data type. Both of these bugs are marked as fixed and ready for 2020 R1. Unfortunately we don’t know when R1 will drop but if I was a betting person I’d guess sometime in March either the week of Xojo.Connect or maybe even later.
If you’re using Classic API then I believe R3.1 is safe(ish). I’ve experienced some oddities in the Constants Editor but I can’t replicate an issue where it reverts the value with no intervention on my part. The new ColorGroup Editor for iOS projects just seems sluggish but that may just be the result of the new ColorPicker. If you’re doing iOS projects you pretty much have to use R3.1 to stay up to date.
I have migrated a few projects to R3.1. A few that I’ve attempted have had compilation issues and I haven’t gone back to determine if they were plugin or code issues and frankly I’m not that big of a hurry to upgrade. R1.1 is still working fine for me and I don’t need the hassles involved with major Xojo upgrades.
So my advice is to test the heck out of your projects if you upgrade to R3.1. I say this every release (because its true) but if you’re using API 2.0 then massive testing is a necessity. I put it this way: do you want to bet your company and/or product on trusting a new API?
What is your experience with 2019 R3.1? Is it worthy? Are you holding back and, if so, why?