Hello,
I have watched all your videos but I am specifically writing here regarding this video: https://sites.google.com/computerplus.gr/alpha360erp-wx/windev-implementation/elements-of-the-ui-win
In this video I observed that every time we assign Window/Form names to the Dynamic structure we tend to write the name of Internal Window as string. Instead of that can't we use Window's name followed by ..Name. Like for example: IWB_Asset..Name.
Coding like this has its advantages. One is that if for any reason we need to rename a window (for any of the million reasons) all that we have to do is rename the window and immediately the Refraction feature of WD will kick in and offer to rename all occurrences in code with the new name. Otherwise what we have to do is find each occurrence and replace it manually.
Just my thoughts.
Yogi Yang
please check https://www.babacrm.com/
Hi Yogi,
I took another look at your suggestion.
Unfortunately this type of code - IWB_Asset..Name - will NOT always work with WINDEV.
The internal window - IWB_Asset - must be "opened" at the time you use IWB_Asset..Name.
Otherwise you get a GPF ...
This happens ONLY with INTERNAL WINDOWS
Regards
Steven Sitas
Hi Yogi,
Just note that you are reffering to v1 documentation and videos - many things have changed in v2.
For a start, everything is now on the main website and not on google sites.
Now regarding your question:
The UI code [the way it works] is shared between all our implementations - currently WX, .Net and Ruby on Rails - so we have to do it in a way that is "cross platform".
A WX developer can of course use ..Name type programming in WX code and have all the advantages you describe.
Regards
Steven Sitas