#20 Provide access to protected vars

[Anonymous]

Exported from Bugzilla, issue 3707.

--- Comment added on 8/20/02 10:25:02 AM ---
Gary Hart, 8/20/2002
[I apologize, I've re-posted this msg to start a new thread for clarity]

For those of us using your components as so much more than a simple HTML
Browser, your design team needs to provide Accesor/Mutator methods to allow
a programmer using your components to have direct access to such things as
the following:
================
TIpHtml.FHotNode
TIpHtmlPanel.MasterFrame
TIpHtmlFrame.HyperPanel
================

I say this because in order to achieve at least two of the functionalities I
was after... your tech support people had to demonstrate for me how to
"hack" into your class hierarchy to have access to the above mentioned
protected variables.

Don't get me wrong.... I am grateful that your personnel are helpful,
creative & smart enough to think about and show me these techniques to
achieve the desired goal... however, as a developer hoping to use your
product in the long term it really makes me worry about the future
possibility of your engineers possibly changing the internals of the objects
(and they would do so without fear since they are protected vars) and
potentially breaking these critical pieces of "hacked-in" code.

You've got a great product here... now let's make it even BETTER!

Gary D. Hart
ghart@compulaw.com