Is PS_GET_PROPERTY and PS_SET_PROPERTY in OI help?

Can you explain these functions? And why use these rather than the GET_PROPERTY and SET_PROPERTY?

PS_GET/SET_PROPERTY are lower level than get/set. There are some items that were not released to get/set and were only available with ps_get/set (i think handle was one .. and even idleproc??).

I think one reason this is not documented it is allows things to change under the covers without causing problems with developer code.

dsig

PS_GET_PROPERTY and PS_SET_PROPERTY are C programs that link into PS and handle managing the properties resident there. VISIBLE, SIZE and other attributes you'd normally associated with Windows™ are parts of PS. Other properties, like CONV, RECORD, SAVEWARN are not part of PS and managed direct by GET_PROPERTY and SET_PROPERTY.

Why use them? Best answer I have is because it's faster. OE doesn;t need to jumping through the hoops of parsing the variables, determining what to do, setting various flags, just to call a C program. Simply faster to call it yourself.

Why not use them? Because it's not documented, and he who lives by the undocumented feature, dies by the undocumented feature. Most importantly though, if the nature of the API changes, then you might have to recode your work. The documented ones will always remain compatible.

For what it's worth, this Sprezz guy never uses them.

[email protected]

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

Thanks for the replies. I now understand.

View this thread on the Works forum...