C / C++ / MFC

14-Jan-12 2:21

You may:
in main.h remove the line

C++

static MYSQL *mysql5;

in DlgLogin.cpp add the line

C++

MYSQL * mysql5;

in income.cpp add the line

C++

extern MYSQL * mysql5;

Now the variable in income.cpp is exactly the same of DlgLogin.cpp so no assignemnt is required.
Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Re: Global variable

1.fcb191314-Jan-12 3:04

1.fcb1913

14-Jan-12 3:04

Thank you. This function. Thumbs Up | :thumbsup:

Re: Global variable

CPallini14-Jan-12 4:19

How to respond to WSAETIMEDOUT in CSsyncsocket::onconnect

14-Jan-12 4:19

Well, I had no doubt about... Big Grin | :-D

You are welcome.

ForNow13-Jan-12 7:07

Re: How to respond to WSAETIMEDOUT in CSsyncsocket::onconnect

13-Jan-12 7:07

I have a two folded question

1) How to respond to

WSAETIMEDOUT

in the OnConnect override for CASyncSocket
where nErrorcode = WSAETIMEOUT

2) My CASyncsocket class "Mysocket" is a member of CWinThread Class as I want to make where
the socket class lives the highest priority

if the answer to question 1 call CASyncsocket::connect again then how would I obtain
my CWinThread class which has my CAsynsocket class a member

for example
MyCAsynSocket* currentthread;
class MyCwinThread : public CWinthread
{
.
.
.
.
CAsynSocket MyCAsynSocket;
CString ipaddr;
UINT port;
}
currentthread = (MyAsynSocket*) = AFxGetthread(): //

currentthread->connect(currentthread>ipaddr,currentthread->port);

Thanks

Chris Meech13-Jan-12 7:22

Chris Meech

13-Jan-12 7:22

Not sure what you are trying to explain or do here, but this line of code looks really incorrect.

currentthread = (MyAsynSocket*) = AFxGetthread(): //

Also in terms of trying to connect again, can you not wrap the connect call within some kind of loop operation? Smile | :)

Chris Meech
I am Canadian. [heard in a local bar]

In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]

posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]

dll loading itself launching the application

appollosputnik12-Jan-12 2:42

appollosputnik

12-Jan-12 2:42

Dear Friends
I am loading a dll from another exe mfc application. for that i have exposed one api 'runAppli' in the dll as extern "C". Then I am loading the dll using LoadLibrary. By loading the dll itself the dll application is launched. I am surprised. I should call the api 'runAppli' and then the application should launch but its not happening. How come it is happening please give some suggestions.

[code]
// in the all
extern "C" BOOL __declspec(dllexport) runAppli(CString filename)
{
AFX_MANAGE_STATE(AfxGetStaticModuleState());
if(filename.IsEmpty())
return false;
view->ShowWindow(SW_SHOW);
view->loadProfile(filename);
view->domainSetUpForProfile();
view->drawLines();
view->drawArcs();
view->drawProfile();
return true;
}

//in the client exe application

void CClientRevolutionProjDlg::OnBnClickedButton1()
{
HINSTANCE hinstLib;
hinstLib = LoadLibrary(L"C:\\Users\\sujan.dasmahapatra\\Documents\\Projects\\Bhagavan_SurfaceRevolution\\RevolutionProj\\debug\\RevolutionProj.dll");
}
[\code]

By simply loading the dll the dll application is launching.. why ??? Thanks Sujan

Re: dll loading itself launching the application

C^hris L^osinger12-Jan-12 3:50

C^hris L^osinger

12-Jan-12 3:50

it's impossible for us to say, without knowing what the DLL has in its DllMain (or CWinApp::InitInstance).

image processing toolkits | batch image processing

Re: dll loading itself launching the application

Randor 12-Jan-12 13:31

Randor

12-Jan-12 13:31

Hi,

The MFC DllMain function will automatically call InitInstance when your DLL is loaded and it also calls ExitInstance when the DLL is unloaded.

You might be able to get around this by providing your own DllMain function:

HOWTO: How to Provide Your Own DllMain in an MFC Regular DLL[^]

I don't really recommend providing your own Dllmain function... you could probably prevent the window creation by modifying your InitInstance and removing/moving the window/view initialization.

Best Wishes,
-David Delaune

Learn MFC

columbos1492711-Jan-12 19:22

columbos14927

11-Jan-12 19:22

Hello,
Ive been programing in MFC for a while.
And now i would like to learn MFC deeper and to understand better what is going on behind the scene.
What good books exist for learning MFC?

Re: Learn MFC

«_Superman_»11-Jan-12 19:46

«_Superman_»

11-Jan-12 19:46

Here are 2 books that I recommend -
Programming Windows with MFC, Second Edition[^]
MFC Internals: Inside the Microsoft(c) Foundation Class Architecture[^]

«_Superman_»
I love work. It gives me something to do between weekends.

Microsoft MVP (Visual C++)

Polymorphism in C

Proper response From WSAEWOULDBLOCK return code From CAsyncSocket::Connect

ForNow11-Jan-12 10:24

Re: Proper response From WSAEWOULDBLOCK return code From CAsyncSocket::Connect

11-Jan-12 10:24

Hi,

I got a

WSAEWOULDBLOCK

return code from the connect method would the proper
response be to retry the operation until I get a Zero return code

CPallini11-Jan-12 10:45

Re: Proper response From WSAEWOULDBLOCK return code From CAsyncSocket::Connect

11-Jan-12 10:45

As MSDN suggests[^]:

If this indicates an error code of WSAEWOULDBLOCK, and your application is using the overridable callbacks, your application will receive an OnConnect message when the connect operation is complete

you shouldn't call again the Connect method because the connect operation is in progress after method returns. Viceversa, you should override the OnConnect method (see the example in its documentation[^]) to know when the connect operation is completed.

ForNow11-Jan-12 14:36

Re: Proper response From WSAEWOULDBLOCK return code From CAsyncSocket::Connect

11-Jan-12 14:36

I did that and i got WSAETIMEDOUT as the nerror code any way to set the time out value for more time

thanks

CPallini11-Jan-12 22:08

Re: Proper response From WSAEWOULDBLOCK return code From CAsyncSocket::Connect

11-Jan-12 22:08

This time it is properly an error and you have to call again the Connect method. I don't know if you may change the timeout value.

ForNow12-Jan-12 12:19

Window does not restore properly.

12-Jan-12 12:19

How about if I set the thread priority where CAsynSocket Class lives to the highest value the highest value

cpp_prgmer11-Jan-12 5:53

cpp_prgmer

11-Jan-12 5:53

I have pop-up dialog that I custom paint in the client rect and show it in the titlebar of my MDI application. Then I use SetWindowPos such that my dialog stays in the desired relative position on the titlebar, whenever the main window is resized\moved.
Everything works fine, except when I minimize the main window. Clicking on the window icon in taskbar does not restore it, but the icon changes to that shown for an active window. I can however right-click on the icon and say "Restore" or "Maximize" to do the same.
Can someone tell me what I am missing? Does it have something to do with WS_CLIPSIBLINGS in the windows styles when its created?

modified 11-Jan-12 12:21pm.

Re: Window does not restore properly.

jkirkerx13-Jan-12 10:53

Closing Program, shutting down c++ win32.

13-Jan-12 10:53

I don't know how you showed it in the title bar?

This is my main window

hWnd = CreateWindow(
        sz_WindowClass,
        sz_Title,
        WS_OVERLAPPEDWINDOW | WS_CLIPCHILDREN | WS_EX_CONTROLPARENT,
        CW_USEDEFAULT, 0,
        CW_USEDEFAULT, 0,
        NULL,
        NULL,
        hInstance,
        NULL
     );

jkirkerx10-Jan-12 10:22

10-Jan-12 10:22

When I close my program in visual studio 2010 running in debug, I notice that I have to stop debug, to fully close the program. So I've been running my compiled exe's and the same thing happens, in which I have to use task Manager to kill the process. The windows close, but the process is still running.

So perhaps I'm missing something in my WndProc.

I have a WM_DESTROY, but I don't have a WM_CLOSE switch

case WM_DESTROY:
PostQuitMessage(0);

This is my File Exit

case IDM_FILE_EXIT:
PostMessage(hWnd, WM_CLOSE, 0, 0);
break;

Luc Pattyn10-Jan-12 10:24

Luc Pattyn

10-Jan-12 10:24

Do you have any extra threads running, that aren't marked "background threads"?

Smile | :)

Luc Pattyn [My Articles] Nil Volentibus Arduum

jkirkerx10-Jan-12 11:27

10-Jan-12 11:27

I'm not sure, but that's a good start or point in the right direction.

Eugen Podsypalnikov11-Jan-12 4:15

Eugen Podsypalnikov

11-Jan-12 4:15

Try "Break" instead of "Stop" for your debug session
and observe the stack(s) of the existing thread(s) Smile | :)

They sought it with thimbles, they sought it with care;
They pursued it with forks and hope;
They threatened its life with a railway-share;
They charmed it with smiles and soap. Smile | :)

jkirkerx11-Jan-12 6:33

11-Jan-12 6:33

That's a good idea

MSG m;
while(GetMessage(&m, NULL, 0, 0)) <-- Break
{
    if (!IsDialogMessage(hUserAccount_Index, &m))
    {
        TranslateMessage(&m);
        DispatchMessage(&m);
    }
}

Mohibur Rashid10-Jan-12 14:11

Mohibur Rashid

10-Jan-12 14:11

Dont post WM_CLOSE message post WM_DESTROY Message

or
Call the PostQuitMessage function under WM_CLOSE case.

Richard MacCutchan10-Jan-12 21:58

Richard MacCutchan

10-Jan-12 21:58

Posting the WM_CLOSE is quite correct.

Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman