Apr 24, 2013 Replies: 2 Now, I know there are some dialogs out there, but I wanted a familiar looking file dialog, so here it is. This is a working demo of the library. I tried to keep the execution as simple as possible. Let me know if you have any problems. View attachment GFileDialog.zip Click to expand...
Now, I know there are some dialogs out there, but I wanted a familiar looking file dialog, so here it is. This is a working demo of the library. I tried to keep the execution as simple as possible. Let me know if you have any problems. View attachment GFileDialog.zip
Vader Well-Known Member Licensed User Longtime User Apr 24, 2013 #2 I know this isn't absolutely on topic, but thank you for extensively using DesignerName in your Library, as it has meant the B4A Object Browser required some bugfixes to support it. :sign0060:
I know this isn't absolutely on topic, but thank you for extensively using DesignerName in your Library, as it has meant the B4A Object Browser required some bugfixes to support it. :sign0060:
agraham Expert Licensed User Longtime User Apr 24, 2013 #3 Vader said: I know this isn't absolutely on topic, but thank you for extensively using DesignerName in your Library, as it has meant the B4A Object Browser required some bugfixes to support it. :sign0060: Click to expand... This is a Basic4android Class compiled obfuscated as a library so it was Basic4android that stuck the DesignerName into the xml.
Vader said: I know this isn't absolutely on topic, but thank you for extensively using DesignerName in your Library, as it has meant the B4A Object Browser required some bugfixes to support it. :sign0060: Click to expand... This is a Basic4android Class compiled obfuscated as a library so it was Basic4android that stuck the DesignerName into the xml.
