on 5/25/04 10:21 AM, Joseph J. Strout at joe at realsoftware dot com wrote:
>> Yes of course there are cases where the dynamic API, but all the
>> cases we have brought up show that there are to many cases that just
>> don't work. Why does it not work for each and every property ?
>
> I don't know. There were some bugs in it earlier in the last beta
> period, but we fixed those. What I'd need now are specific examples
> (preferably filed via the feedback system) of any remaining places
> where it doesn't work, so we can fix them.
Calling "REALLoadGlobalMethod" appears not to be an issue (haven't checked
every possible method), however "REALGetPropValue" is an issue when in
design time.
>
>> Why does it not work in design mode and so on.
Although some guessing is involved here, accessing properties may be related
to a flag that we use when we register properties. If it is
REALpropRuntimeOnly, then it could explain why REALGetPropValue on a
folderParent would fail, because we are not in Runtime, and the prop is
defined only in Runtime. We use REALpropRuntimeOnly when the prop is an
object, to prevent RB from crashing when a user would drag a subclass of
folderitem on the window.
If this is the case, then without breaking existing code, entry point access
may be a very good alternative to get a sanctioned functionality ;-)
>
> I don't know that one either, however as noted last night, it's
> unlikely that you can expect these to work in design mode in RB6
> anyway. Design mode is going to be a much more restricted
> environment than it has been in the past. If you need to do
> something like copy items from a virtual volume into the user's
> project folder, then we should discuss those needs and come up with
> another solution.
Sure, let's take note of this and commit ourselves.
Alfred
_______________________________________________
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|