I found out that in version 3 a method in a module changed scope. That means, when you set the scope of the method to protected or private, you can still call the method outside the module with “MyMethod”.
This is a show stopping bug because it makes a mess of every well developed application.
How is it possible that in version 3.2 this bug is still present?
This is the first time I’ve heard of this bug and I was unable to reproduce it in a new project. Please file a bug report with whatever details you have.
Thank you very much Travis. I am very glad that this will be fixed in the next update.
In the meantime I experimented a little, I added a property to the module too, made it global, protected, private and in all cases it showed normal behaviour. Then I changed the method (MyMethod) again to global, private, global, protected and guess what… it behaved normal again like it should be.
But when I close Xojo, open it again, choose a new desktop project and then follow the steps above again, it behaves again unexpected.
Thank you Xojo for fixing this bug. Nice job done!