If you know of any regressions in the latest version, please post them here. This should help me and others to decide whether moving from previous version to r2 might cause new problems that did not exist with the previous version, or if it’s smarter to wait for a r2.1.
Please note: Regression means bugs that break things that used to work. Please do not post other issues here, as that would only clutter this thread needlessly.
One of my apps has a large screen where container controls are stacked and hidden and shown as needed. This has worked well for several releases of my app with previous versions of Xojo. When built with 2017r2 this still worked and looked good on Mac, but on Win32 the container.visible = false did not correctly hide the container. Simply building the project with Xojo 2017r1.1 corrected the problem and allowed me to release my win32 version.
there are a handful we are aware of that have been reported to us
<https://xojo.com/issue/49172>
<https://xojo.com/issue/49200>
<https://xojo.com/issue/49196>
<https://xojo.com/issue/49190>
<https://xojo.com/issue/49153>
Three of those cases are private and can’t be viewed.
I’d add the Postgres plugin bug to this too, but the workaround is easy.
If you call Connect on an already-connected database, you will start to get odd SQL errors on subsequent calls. Workaround is, don’t do that.
Can you post sample code of the workaround? 
They’re visible to pre-release testers
And thats easy to join https://forum.xojo.com/conversation/post/311507
I just added this one <https://xojo.com/issue/49255>.
I’m hoping that it’s just me and/or that there’s an easy workaround else my next release is effectively stalled.
[quote=346656:@Norman Palardy]there are a handful we are aware of that have been reported to us
Feedback Case #49172
Feedback Case #49200
Feedback Case #49196
Feedback Case #49190
Feedback Case #49153[/quote]
[quote=346691:@Jason Tait]I just added this one <https://xojo.com/issue/49255>.
[/quote]
Huh
Testing suggests this hasn’t worked since 2012r2.1 so its not really a regression
[quote=346756:@Norman Palardy]Huh
Testing suggests this hasn’t worked since 2012r2.1 so its not really a regression[/quote]
I disagree.
If you Google “software regression” you’ll see that a regression is a bug that makes a piece of software stop working as intended after a certain event, such as a software update. There are slight variations on this form but that’s the intent in all the definitions I could find.
While I didn’t go and test 2012r.1 I’ve never owned nor used that version I did test the previous version 2017r1.1. This bug does not occur in that version. It occurs after the most recent software update.
When I reported the bug, I ticked the box in the Feedback app to confirm that “This worked in a previous version” and Feedback added the comment “Regression: Yes” to the top of my bug report. So it seems that the author of Feedback also understands the definition of a regression.
I don’t get paid to test Xojo but I do so because I like and use the product and bugs affect my work. Plus @Geoff Perlman and the other Xojo staff I’ve dealt with seem like good people so I want to help them be successful.
But I’m busy with my own work too, so having to explain all of this to you just wastes more of my time. Oh and the occasional “thank you”, while not required, wouldn’t hurt either. It’s not personal. It’s just a bug report.
Our QA persons report on that bug report says they find this behaves this way back to 2012r2.1
Hence “not a regression in the current version compared to the prior one”
It is a regression in the current version compared to the prior one.
I guess we should ask, “Which prior one?” as what Norman is saying is this behavior of PagePanel goes back as far as 2012r2.1
As I said above:
So now that this is clear to all, it seems the QA persons report is incorrect. PagePanels can be reordered in 2017r1.1 and fail to be reordered in 2017r2.
Which, I agree with you, is a regression.
(sorry for butting in, I was just trying to understand so I know which version I need to use if I ever need to reorder panels)
[quote=346842:@Norman Palardy]Our QA persons report on that bug report says they find this behaves this way back to 2012r2.1
Hence “not a regression in the current version compared to the prior one”
The rest of your reply gets an ignore[/quote]
Nice Norman. I’d suggest just ignoring it, saying it sounds a bit … offish.
Some things on this forum I don’t take as gospel until I have seen it for myself.
[quote=346850:@Tim Parnell]So now that this is clear to all, it seems the QA persons report is incorrect. PagePanels can be reordered in 2017r1.1 and fail to be reordered in 2017r2.
Which, I agree with you, is a regression.[/quote]
Just tested it on windows, I can reorder in 2017r1.1 but not 2017r2, Jason is right, this is a regression.
@Jason Tait Thanks for that report. Will keep off 2017r2 since I rely heavily on PagePanels and don’t want to run into that. I just reorganized a PagePanel last week.
Yes, it is a regression. Interesting that the “QA Person” Norman mention thought it was from back in 2012r2.1 - not being able to reorganize PagePanels for 7 years would have been noticed… Just because that particular PagePanel Edit window wasn’t touched in the source-control doesn’t mean the functionality is still working…