comp.lang.idl-pvwave archive: archive » Communication between top-level bases.

Home » Public Forums » archive » Communication between top-level bases.

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Communication between top-level bases. [message #11911 is a reply to message #11842]

Tue, 02 June 1998 00:00

Struan Gray
Messages: 178
Registered: December 1995

Senior Member

mirko_vukovic@notes.mrc.sony.com writes:

[widget state as object in uvalue]

> But does anyone else see any other practical advantages?

Make it a 'state' object within a container. That way external
users who want to store information in the user value can do so too.
They have to learn your programming convention for getting and setting
info in the container object but that's better than forbidding them to
touch the uvalue because you've monopolised it.

Pre objects I used to make the uvalue a pointer (or handle) to the
start of a linked list for just this reason. I'm swapping to objects
but haven't settled on a definite plan as yet. Of course, another big
benefit of using heap variables of any kind is that they are globally
available if you can find some way of passing the variable reference
around. It's a nice way to keep track of display preferences for
example.

Struan

Report message to a moderator

[Message index]

		Communication between top-level bases. By: Imanol Echave on Fri, 29 May 1998 00:00
		Re: Communication between top-level bases. By: Struan Gray on Tue, 02 June 1998 00:00
		Re: Communication between top-level bases. By: mirko_vukovic on Tue, 02 June 1998 00:00
		Re: Communication between top-level bases. By: davidf on Mon, 01 June 1998 00:00
		Re: Communication between top-level bases. By: David Foster on Mon, 01 June 1998 00:00

Previous Topic:	CASE tools?
Next Topic:	Re: Concurrent widget program.

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 11 21:05:15 PDT 2025

Total time taken to generate the page: 1.35750 seconds