Hi Przemek,
Okay, this makes things clear.
Not any request from me, and I think this way
it's clean and perfectly well (and better than
the xhb API for sure).
Brgds,
Viktor
On 2008.08.06., at 22:05, Przemyslaw Czerpak wrote:
On Wed, 06 Aug 2008, Szakáts Viktor wrote:
Hi Viktor,
I'm forwarding one recent message I received
in my local mailbox (plus my answer to it).
The topic is some missing xhb class related
API functions.
I'm not saying to include these before 1.0.0
or include them at all, but here it is for
further consideration. In any case, I'd give
these functions better names.
I was taking about it with Maurizio and finally I added:
2008-07-31 17:41 UTC+0200 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
+ adding 2-nd parameter to __clsGetProperties()
When it's TRUE then __clsGetProperties() returns also exported
messages which have corresponding assign messages (with "_"
prefix)
+ added __objGetProperties( oObject, [ lAllExported = .F. ] ) ->
aMsgAndValues
This function returns list of PROPERTY message with their values,
when 2-nd parameter is true it also returns exported messages
which
which have corresponding assign messages (with "_" prefix)
This function is designed to use in object inspectors.
what seems to address the problem much better then using
__ObjGetValueDiff() in xHarbour which was not designed to
write object inspectors and has some serious bugs.
If there are some other suggestions or extensions requests
then we can talk about them and I can implement what we agree.
best regards,
Przemek
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
