Advanced Visual C++ DLL

Closed Posted Jan 17, 2005 Paid on delivery
Closed Paid on delivery

Let's suppose that we are in Visual Basic IDE and we have insert a UserForm named Form1. So untill now, we have Form1 and Visual Basic 'ToolBox' window (that contains available controls). From the 'ToolBox' window we can drag on the Form1 different controls. Let's suppose that, from the 'ToolBox' window we are added on the Form1 a control named Command1. In Visual Basic IDE, when we double-click on Command1 we obtain event:

Private Sub Command1_Click()

'and we can add code in here, like:

MsgBox "You have clicked on Command1 Button"

End Sub

So, in fact, what do I want? I want a Visual C++ control, (that is a container in fact), with two states: Design Time State and RunTime State.

When I put this control on a Visual Basic Form I can drag different controls on this Visual C++ control. I can resize those controls that I added, and do whatever things, that I normally do with controls in Visual Basic IDE. All this are happening at Design Time State, that is a property for this Visual C++ control.

When I select RunTime State property for this Visual C++ control, this control acts like Visual Basic IDE in RunTime Mode, meaning this Visual C++ control (that is a container in fact) let me to add code for all events which other controls on it do have (like, suppose we have a Command1 control on this Visual C++ control. We will have the following events for Command1. Fo example: Command1_Click, Command1_DblClick, Command1_KeyUp, Command1_MouseMove, etc).

Because we don't know what possibly events a child control can have, these events must be executed at RunTime.

There is no alternative, that I write these events at Design Time Mode. Those events that a child control can have, must be stored in an array or something for this Visual C++ control, and I will can execute them, after compilation, even I never wrote code for Command1_Click at Design Time Mode or in Visual Basic IDE.

## Deliverables

1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.

2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):

a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.

b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.

3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).

## Platform

All 32 Bit Windows Platforms:

Windows 95, Windows 98, Windows Millenium, Windows 2000, Windows NT, Windows XP, Windows Longhorn

C Programming Chrome OS Engineering Linux Mac OS Microsoft MySQL PHP Software Architecture Software Testing UNIX Windows Desktop

Project ID: #3522419

About the project

Remote project Active Apr 25, 2005