Nested modules is a must for Xojo that already misses basic things like local functions and local classes (writing functions inside functions and nesting classes inside other classes).
Q: We have folders, so why this is important?
A: Modules have scopes and folders not. So you can hide large and complex private functionality from the outside world while allowing a parent public module expose the public “interfaces” to the public functionality. It’s a kind of nesting folders but with scope hierarchy.
I’ve noticed that the pointed clash was in Module.Name, another guy had a problem in code, also broken, due to his “Object.Name” that always worked before. Some Gremlin seems introduced in the naming of things. Here is the Gremlin: https://forum.xojo.com/57207-smtp-secure-socket-r2019-2-1
[quote=465197:@Greg O’Lone]@Lars Lehmann - Do you happen to have a folder at the same level as the Module with the exact same name?
[/quote]
No, I don’t.
What I made is, I completely recreated the module and compiled it after each step. Took me two hours of work, but now I have the module structure I wanted.
It seems that copying methods into nested modules are responsible for this bug.
Was still broken. As I mentioned, this is something we already knew. And as you can see in Screenshot, all methods are yellow, which means they are protected.
Edit:
the property in the screenshot was also protected. The color just applies if you change it again (which seems to be a bug as well).
And it still doesn’t work after manually re-setting the property scope? I improperly said earlier that the Copy/Paste bug only effects methods, and was just testing and found that it applies to all. Once I reset scope manually, I was then able to run my test project.
I would verify that. Copy & Paste will often just use whatever the original values are, but it wouldnt surprise me if the Navigator is trying to be smart and only displaying what they should be.