1  |   Order by index

Nov 22, 2000, 6:00am

This is a multi-part message in MIME format.
--------------DB49AE3DE9BB98281DD187B6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

oops posted in wrong group probably for that
message

--------------DB49AE3DE9BB98281DD187B6
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <3A1B5955.D23F0678 at yahoo.com>
X-Mailer: Mozilla 4.5 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: sdk
Subject: VB OCX how do you add properties?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 199.174.221.84
From: "the derek" <ImTheDerek at yahoo.com>
Date: 22 Nov 2000 00:52:01 -0500
X-Trace: 22 Nov 2000 00:52:01 -0500, 199.174.221.84
X-Authenticated-User: the derek
Path: server1.Activeworlds.com!199.174.221.84
Xref: news sdk:2866

ok many of you know about the plugin bot im doing.
im making a sort of sdk in ocx form. does anyone
know how to add properties to ocx controls? i
havent made many ocx controls before....


--------------DB49AE3DE9BB98281DD187B6--

Nov 22, 2000, 4:11pm

Are you actually writing the control in VB or in C/C++ for use in VB?

(may not have been paying enough attention to the original posts)

Grims


[View Quote]

Nov 22, 2000, 5:09pm

im writing it in vb

[View Quote] > Are you actually writing the control in VB or in C/C++ for use in VB?
>
> (may not have been paying enough attention to the original posts)
>
> Grims
>
[View Quote]

Nov 22, 2000, 5:26pm

You just add a public property like any other class (Tools | Add Procedure
in VB 5).

Select "Property" as the type ... if it is a read-only property, just delete
the "Property Let" procedure.

VB looks after the rest. Use the procedure attributes (again under the Tools
menu in VB5) if you want to tune it a bit (set to default property etc.). It
should automatically appear in the properties box for the control as soon as
you close the exit the control's visual builder window.

Grims


[View Quote]

Nov 22, 2000, 5:39pm

ok... but what are property pages?
and what d i put under the get and let propertes.... ive tried that before and
well it didnt work too well thats all i have t say ohmwell ill try again

[View Quote] > You just add a public property like any other class (Tools | Add Procedure
> in VB 5).
>
> Select "Property" as the type ... if it is a read-only property, just delete
> the "Property Let" procedure.
>
> VB looks after the rest. Use the procedure attributes (again under the Tools
> menu in VB5) if you want to tune it a bit (set to default property etc.). It
> should automatically appear in the properties box for the control as soon as
> you close the exit the control's visual builder window.
>
> Grims
>
[View Quote]

Nov 22, 2000, 5:49pm

OCX controls are classes. If you don't know how to use classes in VB you
shouldn't be dealing with controls yet.

Read the manual and the help files and/or use web-based resources like
www.vbweb.co.uk to learn about the language first. Building controls in VB
should be very simple - very "fat", but very simple - as long as you have
the grounding in the technologies it is based on.

Grims.


[View Quote]

Nov 22, 2000, 7:38pm

Another thought on this... since you need to understand the classes to write
this anyway, why not just create your "plug-in bot" as a class or set of
classes in an ActiveX DLL? MrGrimms AwSdkOcx2 control had to be an OCX
because he had to map the C events and callbacks in the AW SDK into VB
(since you can't access them directly. You already have all you need within
the VB environment, so it seems unnecessary to create a visual control for
something that is non-visual.

Grims.

[View Quote]

Nov 22, 2000, 7:44pm

i have lrn edition of vb cant make dlls the only reason i can make ocx is caus
ei downloaded the control creation edition of vb of ms site

[View Quote] > Another thought on this... since you need to understand the classes to write
> this anyway, why not just create your "plug-in bot" as a class or set of
> classes in an ActiveX DLL? MrGrimms AwSdkOcx2 control had to be an OCX
> because he had to map the C events and callbacks in the AW SDK into VB
> (since you can't access them directly. You already have all you need within
> the VB environment, so it seems unnecessary to create a visual control for
> something that is non-visual.
>
> Grims.
>
[View Quote]

1  |   Order by index