Results 1 to 4 of 4

Thread: Global Multiuse Object

  1. #1

    Thread Starter
    transcendental analytic kedaman's Avatar
    Join Date
    Mar 2000
    Location
    0x002F2EA8
    Posts
    7,221

    Question

    How do i refer to it?
    I'm trying to add it in a script control and i think if i use new keyword it will just create another instance instead of getting the original global object.
    Use
    writing software in C++ is like driving rivets into steel beam with a toothpick.
    writing haskell makes your life easier:
    reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
    To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.

  2. #2
    Serge's Avatar
    Join Date
    Feb 1999
    Location
    Scottsdale, Arizona, USA
    Posts
    2,744
    Are you refering to a DLL when you say object? If yes, then I don't think it's possible, since you have to specify the Instancing settings before you compile it.

  3. #3
    Addicted Member
    Join Date
    Oct 2000
    Location
    Vienna/Austria
    Posts
    132
    Hi kedaman !!!

    Do a search on MSDN on following articles in Visual Basic Concepts:

    1) Instancing for Classes Provided by ActiveX Components
    (is an explanation where you can use the "globalmultiuse")
    2) Global Objects and Code Libraries
    (include an example)
    3) Guidelines for Creating Root Objects
    (another Tip of globalmultiuse)

    maybe this help you out of your problem.

    -cu TheOnly

  4. #4

    Thread Starter
    transcendental analytic kedaman's Avatar
    Join Date
    Mar 2000
    Location
    0x002F2EA8
    Posts
    7,221
    Well, dunno if i really need this now, i got a workaround by making a function on the global mu class returning me keyword. But i think i abandon this idea...
    Use
    writing software in C++ is like driving rivets into steel beam with a toothpick.
    writing haskell makes your life easier:
    reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
    To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width