I had a type set to two modules, with identical name. Everything was working great. I cannot remember the error I was getting and what was my b4a version then, but I had to declare the second type using a different name.
After upgrading to the latest b4a version, I've noticed a problem with casting. I was sending with callSub2 the type from one activity module to the other. Though they had identical components, the error was there. Now, removing one type from the second activity, and renaming it to its original name, everything is running smooth again. So far, so good, I think that with this b4a version types are declared globally. Yet, I still wonder if there is a deeper reason for the casting error with the two types of identical components. Any help would be appreciated.
After upgrading to the latest b4a version, I've noticed a problem with casting. I was sending with callSub2 the type from one activity module to the other. Though they had identical components, the error was there. Now, removing one type from the second activity, and renaming it to its original name, everything is running smooth again. So far, so good, I think that with this b4a version types are declared globally. Yet, I still wonder if there is a deeper reason for the casting error with the two types of identical components. Any help would be appreciated.