C CaptKronos Active Member Licensed User Longtime User Mar 30, 2019 #1 (Not sure if this is reporting a bug or making a wish.) As per this post https://www.b4x.com/android/forum/threads/xui-views-causing-compiler-error.104310/ in a project that uses XUI Views, creating the following declaration causes a compile error. B4X: Type item(index As Int, text As String) In fact the actual definition of item doesn't matter, it's the name 'item' that causes the problem. I believe it would be useful if the IDE (or the compiler with a more obvious error) could flag up these clashes.
(Not sure if this is reporting a bug or making a wish.) As per this post https://www.b4x.com/android/forum/threads/xui-views-causing-compiler-error.104310/ in a project that uses XUI Views, creating the following declaration causes a compile error. B4X: Type item(index As Int, text As String) In fact the actual definition of item doesn't matter, it's the name 'item' that causes the problem. I believe it would be useful if the IDE (or the compiler with a more obvious error) could flag up these clashes.
C CaptKronos Active Member Licensed User Longtime User Jun 27, 2019 #3 I have just noticed that this bug still exists in v5.81.
Erel B4X founder Staff member Licensed User Longtime User Jun 28, 2019 #4 This is not exactly a bug. B4xlibs are compiled together with your app. The conflict happens because XUI Views code use the 'Item' identifier as a variable name.
This is not exactly a bug. B4xlibs are compiled together with your app. The conflict happens because XUI Views code use the 'Item' identifier as a variable name.
C CaptKronos Active Member Licensed User Longtime User Jun 28, 2019 #5 Do you think it would be possible to introduce a more obvious error message?
Erel B4X founder Staff member Licensed User Longtime User Jun 30, 2019 #6 This error will not happen in the next version of B4i.