C / C++ / MFC

22-Oct-07 3:30

Hi,

My project has a Modal dialog box(first dialog box)
1)First dialog box consist of a button, on clicking that button another modal dialog box(second dialog box) opens.
2)First dialog box also consist of tab control which consist of two tabs.Each tab has modelless dialog box.
My question is when i open the second dialog box(opens on pressing the button) the control will be with second dialog box as it is a modal dialog box but when i place it on one of the tab dialog box(the dialog size of the second dialog box is smaller than the dialog box on the tab) and a mouse click on the tab dialog box the control goes to tab dialog box,.Why?? How to avoid this. The second dialog box should have the control until i close it.
I hope you people got my quesion.

Thanks in advance

David Crow22-Oct-07 3:38

David Crow

22-Oct-07 3:38

What is the parent/owner relationship between the first and second modal dialog boxes?

"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman

"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

shir_k22-Oct-07 3:46

22-Oct-07 3:46

Thanks for reply.
First dialog box is a main application(User interface for the user).second dialog box is, if the user wants to change the COM port settings like baud rate or parity he has to open second dialog box which can be opened by pressing the button on the main application.

David Crow22-Oct-07 3:51

David Crow

22-Oct-07 3:51

It matters not what they are used for. What is the parent/owner relationship between the first and second modal dialog boxes? Just because dialog A opens dialog B, that does not also imply that dialog A is the parent of dialog B, or that dialog B is owned by dialog A.

shir_k22-Oct-07 4:04

22-Oct-07 4:04

You are asking style of the window. Both are popup window style.
I hope i have answered your question if not let me know in detail.Am not getting what does parent/owner relationship means.Even tab windows are popup style.

shir_k22-Oct-07 4:24

22-Oct-07 4:24

Nelek22-Oct-07 4:27

22-Oct-07 4:27

Ok.

Are you using resource editor? or coding all by yourself?

Greetings.

--------
M.D.V.

If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?

Help me to understand what I'm saying, and I'll explain it better to you

Wink | ;)

shir_k22-Oct-07 4:33

22-Oct-07 4:33

Am using resource editor(MFC SDI project)

Disallowing dll use from development environment?

Nelek29-Oct-07 21:44

Nelek

29-Oct-07 21:44

Then in the button to do the call, try it like:

void CMyButton::OnClick ()
{
CMySecondDlg newDlg;
if (IDCANCEL == newDlg.DoModal ())
return;

//More code
}

electronica80822-Oct-07 2:53

Re: Disallowing dll use from development environment?

22-Oct-07 2:53

Hypothetically, is there a way to create a DLL that will only work at runtime? Any attempt to use the DLL from a development environment would fail?

I am investigating some ways to protect intellectual property.

Any input would be greatly appreciated.

Cedric Moonen22-Oct-07 2:55

Cedric Moonen

22-Oct-07 2:55

And what is the problem when loading your dll if the project is executed from the IDE ?
Did you think about distributing the release version of your dll ?

Cédric Moonen
Software developer

Charting control [v1.2]

Re: Disallowing dll use from development environment?

electronica80822-Oct-07 3:26

Re: Disallowing dll use from development environment?

22-Oct-07 3:26

Here is a hypothetical example...

Fred spends years developing a DLL to do intense mathematical computations. Bob buys a license to develop against and distribute Fred’s DLL with Bob’s application. Fred is worried other people will use his DLL in their own applications.

Just compiling the DLL in release mode will not stop people from using the DLL in Visual Studio, and releasing an application that uses it.

Is there any way to do this?

C^hris L^osinger22-Oct-07 3:36

C^hris L^osinger

22-Oct-07 3:36

electronica808 wrote:
Is there any way to do this?

how can anyone, even licensed customers, use your DLL if they can't use it inside an IDE ? do all your users have to develop via command line ? i, for one, would hate hate hate hate hate using a DLL that tried to enforce such a restriction - even though i think it's probably not possible to do.

what about just making the user 'initialize' the DLL with a license key that you issue?

image processing toolkits | batch image processing

Re: Disallowing dll use from development environment?

electronica80822-Oct-07 3:49

Re: Disallowing dll use from development environment?

22-Oct-07 3:49

Thanks for the reply.

Since Bob has paid, he should be able to use the DLL from the development environment and release his applications.

I am thinking this probably is a pretty common scenario. I was wanting to see what developers are doing currently to protect their intellectual property.

I had thought of the initialization key as a rudimentary way to pull this off. I wondered if there were any more solutions to this.

Nelek22-Oct-07 4:23

Nelek

22-Oct-07 4:23

I think this is the biggest problem with "portability" of DLLs. Are very comfortable but, on the other side...

I guess the only thing you can do to protect the use of some functions and allow them only in an application... is to do it inside the application. As a new module/class, and asking for license or password before executing. But in a dll...

Re: Disallowing dll use from development environment?

C^hris L^osinger22-Oct-07 4:28

C^hris L^osinger

22-Oct-07 4:28

electronica808 wrote:
Since Bob has paid, he should be able to use the DLL from the development environment and release his applications.

but there will be no way to evaluate the DLL in an IDE ? if not, that will certainly turn off potential customers.

we use init keys, it works fine.

we've also done separate trial and licensed builds. that's a bit more secure but it doubles the number of binaries you have to build, test and distribute, as well as requiring a scheme to restrict access to the licensed builds (ex. a password-protected web folder).

i've seen DLLs that require you to get a license key for the individual machine , and the DLL will then only run on that particular hardware. that's fine if your app is running on a web server (one machine, many users), but unworkable for distributed apps.

-c

image processing toolkits | batch image processing

Re: Disallowing dll use from development environment?

Peter Weyzen22-Oct-07 19:39

Peter Weyzen

22-Oct-07 19:39

If Bob doesn't pay, he uses this DLL in his product and he's making lots of $$$.

Sue him.

People who are going to make money from their products, often want their software to be legal. I know that we read the licensing documents with every bit of software we use.

That's protection enough for me.

If he's not making any (or much) money, don't worry about it.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br />
Peter Weyzen<br />
Staff Engineer<br />
<A HREF="http://www.soonr.com">SoonR Inc -- PC Power delivered to your phone</A>

Re: Disallowing dll use from development environment?

electronica80822-Oct-07 5:18