reporting a bug is usually first step, even twice !
But what could you suggest to do if Xojo says bug is fixed 3 times in 2024 but it’s still there?
Is this a strategic behaviour or what?
still same problem here, .visible property is not working as it should
my point of view how the process could be done:
the issue author get an IDE update and xojo team would call if problen is fixed or not
and based on the answer the status of ticket is changed or updated.
if not available by call use e-mail or forum communication.
TeamViewer, RustDesk, Remote Desktop can be used for support too.
creating an issue by calling a xojo developer team member would reduce duplicates of new issues.
currently the issue system is flooded uncontrolled by everybody.
Need to create new issue (even if it is 4x or more) until is finally fixed.
Make it soon, they may be testing next Xojo version as we speak.
Participate as a beta tester, make sure the issue is fixed before next release (test the beta build when they say is fixed and confirm is fixed).
this could be a automated nightly build
Does it means that QC is done only externally by volunteers (unpaid and time counted) and no professionals?
At least they could ask the author that filed the bug.
Last words of Geoff in december were that Williams was working on it… So Williams works bad or beta tester is not trustworthy
William worked on the case and fixed something. Maybe it was not fixed all that is causing the problem, that’s why they ask question to the OP that create the issue. Some bugs can cause different problems or consist on different bugs.
Beta testers usually test their own issues and make sure that their programs work on new version of Xojo. They don’t review all the issues reported.
I’m sure if you are willing to test beta versions for issues that are important to you, you will get a better product.
sure, who should I contact?
Next to your Name here in the forum it says ‘Testers’ 
so it looks like you are part of the testers group. If you can visit this forum section, you already are a tester. If not, then email them.
Thank you, installed and verified latest version still same problem.
Made a post, here the link
Hope some reasonable takes it in account after so many years to fix this horrible bug