I'm working on a service that handles resizing of our
application. DataWindows should get some special treatment,
and for that I need a way to get all the *controls* in the
DW. I know I can use DataWindow.Objects to get the complete
list of objects, and then check them all to see which are
controls and which are not. Looking for a more efficient
way, I came across a thread where the property VisualObjects
was mentioned. I've tried it, and it works just fine.
However, it is undocumented, and I'm a bit reluctant about
using such a feature in such a fundamental service.
The question is, then, whether this feature has not been
documented by mistake and could safely be used, or the lack
of documentation is by purpose, which means the feature
might not be supported in future versions. Does anyone have
an idea what is the case?
Subject: Can DataWindow.VisualObjects property be safely used?
X-Mailer: WebNews to Mail Gateway v1.1t
Date: 2 Nov 2008 04:57:42 -0800
X-Trace: forums-1-dub 1225630662 10.22.241.41 (2 Nov 2008 04:57:42 -0800)
X-Original-Trace: 2 Nov 2008 04:57:42 -0800, 10.22.241.41
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:88089
Article PK: 417345
Subject: Re: Can DataWindow.VisualObjects property be safely used?
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
Date: 5 Nov 2008 15:54:45 -0800
X-Trace: forums-1-dub 1225929285 10.22.241.152 (5 Nov 2008 15:54:45 -0800)
X-Original-Trace: 5 Nov 2008 15:54:45 -0800, vip152.sybase.com
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:88110
Article PK: 417365
As with anything, if it is documented it may change, but the change is
unlikely to break backward compatibility. If it is undocumented it is still
unlikely to change, but more likely. If the performance savings aren't
dramatic I'd stick with the DataWindow.objects, which is very unlikely to