C / C++ / MFC

Re: Global Variable Question

19-Mar-06 13:42

I can see this solution:

In the first DLL, define a function that returns a pointer to your variable. In the other DLL, dynamically load the first DLL with a call to LoadLibrary, and call the aforementioned function.

Rich

JSadleir19-Mar-06 14:03

JSadleir

19-Mar-06 14:03

Thanks Rich

That sounds like the way to do it. I'll have a go at it. The variable may, however, revert to null once the function that performs the calculation goes out of scope.

Regards

Jeremy

Re: Global Variable Question

Chris Gao19-Mar-06 13:49

Chris Gao

19-Mar-06 13:49

Hi Jeremy,

I am new to programming too. I think it is really cool to code something in MS Office. I mean that.

Well, I think neither of my suggestions work in your case. Em... is your variable accessed very frequently? I mean, how about use registry table to story this variable?

The following example really do very well in registry access stuff.

http://www.codeproject.com/system/CRegistry.asp[^]

Regards,

Chris

CSockets and multithreading

softwaremonkey19-Mar-06 11:06

softwaremonkey

19-Mar-06 11:06

Hi,

Is there a problem writing to a CSocket from a different thread than the one that created it?

I am sending large files so I use a worker thread to do the writing, but it ASSERTS when it check the handle for the socket.

If I call the code from the same thread it seems OK.

TIA

Tony

Re: CSockets and multithreading

Richard Andrew x6419-Mar-06 11:20

Re: CSockets and multithreading

19-Mar-06 11:20

Don't take this as the final word on the subject, but I do remember reading specifically in the MFC docs that MFC objects cannot be shared between threads.

( I know, this is a real bummer. )

The solution is to pass the handle of the underlying socket to the worker thread, and then have the worker thread create a new CSocket, and Attach() the passed handle.

Hope this helps,
Rich

softwaremonkey19-Mar-06 11:33

softwaremonkey

19-Mar-06 11:33

Hi,

Thanks for the quick reply. You know I think you are right there, I should have realised becasue I have seen similar problems before with MFC objects!

I will try it the way you have suggested tomorrow. Right now I need sleep Sleepy | :zzz:

Thanks again

Tony

Re: CSockets and multithreading

Richard Andrew x6419-Mar-06 11:47

Where is call for DLL within VisStu 6.0 C++

19-Mar-06 11:47

When you wake up, here is some reading for you straight from the MSDN Library:

Windows Handle Maps

As a general rule, a thread can access only MFC objects that it created. This is because temporary and permanent Windows handle maps are kept in thread local storage to help maintain protection from simultaneous access from multiple threads. For example, a worker thread cannot perform a calculation and then call a document's UpdateAllViews member function to have the windows that contain views on the new data modified. This has no effect at all, because the map from CWnd objects to HWNDs is local to the primary thread. This means that one thread might have a mapping from a Windows handle to a C++ object, but another thread might map that same handle to a different C++ object. Changes made in one thread would not be reflected in the other.

There are several ways around this problem. The first is to pass individual handles (such as an HWND) rather than C++ objects to the worker thread. The worker thread then adds these objects to its temporary map by calling the appropriate FromHandle member function. You could also add the object to the thread's permanent map by calling Attach, but this should be done only if you are guaranteed that the object will exist longer than the thread.

Another method is to create new user-defined messages corresponding to the different tasks your worker threads will be performing and post these messages to the application's main window using ::PostMessage. This method of communication is similar to two different applications conversing except that both threads are executing in the same address space.

For more information about handle maps, see Technical Note 3. For more information about thread local storage, see Thread Local Storage and Using Thread Local Storage in the Platform SDK.

printing bitmaps

Waldermort19-Mar-06 8:01

Waldermort

19-Mar-06 8:01

I am trying to implement print and print-preview into a non-MFC application. After a little effort I have managed to create the print-preview function and a non working print function.

I have created a function which is passed a rect for the dimensions and a hdc, this function then creates and returns a HBITMAP compatible with the hdc and the size stated in the rect. I hope to use this function for both print and print preview.

The print preview is simply a dialog box, the HBITMAP is then drawn into the client area.

I'm having problems now trying to correctly draw this bitmap to the hdc returned by printDlg(). I have read all of the (MFC only) projects here on codeproject, but I am left even more confused. I know that I need to stretch the bitmap but all I am left with is a tiny black square.

This is a portion of the print function:

    printRect.bottom = GetDeviceCaps(pd.hDC, HORZRES);
printRect.right  = GetDeviceCaps(pd.hDC, VERTRES);

StartDoc(pd.hDC,&di);
StartPage(pd.hDC);

HBITMAP table = create_printable_table(pd.hDC,&tmprect,rec);
SelectObject(buf,table);
StretchBlt(pd.hDC,0,0,printRect.right,printRect.bottom,buf,0,0,tmprect.bottom,tmprect.right,SRCCOPY);

EndPage(pd.hDC);
EndDoc(pd.hDC);

Please help me with this one, I have spend far too long splitting hairs Frown | :(

-- modified at 14:02 Sunday 19th March, 2006

Re: printing bitmaps

David Crow19-Mar-06 9:04

David Crow

19-Mar-06 9:04

I had a similar problem with one of my projects. Read up on these functions:

SetMapMode(MM_ISOTROPIC);
SetWindowOrg(m_BmpInfo.bmWidth / 2, m_BmpInfo.bmHeight / 2);
SetViewportOrg(pDC->GetDeviceCaps(HORZRES) / 2, pDC->GetDeviceCaps(VERTRES) / 2);
SetWindowExt(m_BmpInfo.bmWidth, m_BmpInfo.bmHeight);	
SetViewportExt(pDC->GetDeviceCaps(HORZRES), pDC->GetDeviceCaps(VERTRES));

"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain

"There is no death, only a change of worlds." - Native American Proverb

Re: printing bitmaps

Roger Allen19-Mar-06 12:24

Roger Allen

19-Mar-06 12:24

Most printer DC's dont support bitblt. You need to use StretchDIBits. Thats why it works in preview (a screen DC) and not in print mode.

If you vote me down, my score will only get lower

Re: printing bitmaps

Hamid_RT19-Mar-06 17:09

Hamid_RT

19-Mar-06 17:09

Hope I understood your question
you need to print bitmap

HDC hdcPrint=CreateCompatibleDC(
CreateDC(pPrinter->pDriverName,(LPCTSTR)lpdevmode->dmDeviceName,pPrinter->pPortName,lpdevmode));
...
...
...

//function print
{

DOCINFO di;

memset((void *)&pd, 0,sizeof(PRINTDLG));
pd.lStructSize = sizeof(PRINTDLG);
pd.hwndOwner = this->m_hWnd;
pd.Flags =PD_RETURNDC|PD_ENABLESETUPTEMPLATE;
pd.hInstance = NULL;
pd.nMaxPage=1;
pd.nMinPage=1;
pd.nCopies=1;
pd.hDevMode=lpdevmode;
pd.nFromPage=1;
pd.nToPage=1;
PrintDlg(&pd);

di.cbSize = sizeof(DOCINFO);
di.lpszDocName = "Job";
di.lpszOutput = NULL;

SelectObject(hdcPrint,hBitmap);
StartDoc (pd.hDC, &di);
StartPage (pd.hDC);

BitBlt(pd.hDC,150,300,2100,1575,hdcPrint,0,0,SRCCOPY);

EndPage (pd.hDC);
EndDoc (pd.hDC);

DeleteObject(hBitmap);
}

maybe it is some helpful to you

Robert Palma Jr.19-Mar-06 7:45

Robert Palma Jr.

19-Mar-06 7:45

Hi,
I am working with tool set template (C++ code for Vis.Stu. 6.0). I will pattern my own code after this template.

The template calls a DLL.

In the past when I have called DLLs from my code I have used the:
LoadLibrary(something.DLL);

But I can't find anywhere in the project's code (all the .cpp. .h .c files) where the DLL is loaded.

When I compile the app everything wokes fine so the DLL is working.

Also, when I do a text search on the project directory, I do indeed find the DLL in the files:
.ilk .plg .dsp .pdb and the .exe

I just can't dinf, within the Visual Studio user interface, where the DLL is declared/called/loaded.

Many thanks,
Robert Smile | :)

Richard Andrew x6419-Mar-06 7:55

19-Mar-06 7:55

Is it possible that the DLL is statically linked to the application at the compile stage, and not dynamically loaded with a call to LoadLibrary?

Look in the project's Properties dialog box and see if the DLL lib file is listed as a dependency.

Robert Palma Jr.19-Mar-06 8:11

Robert Palma Jr.

19-Mar-06 8:11

Troposphere,

Many thanks for reply/answer.

Indeed you are correct:

In Project Settings | PreLink Tab:
The something.DLL is copied from a source location into
the Debug dir.

In Project Settings | Link Tab:
the something.LIB file is referenced.

I am a bit unclear Frown | :-(

on the difference between the
.LIB and the .DLL

Thanks again,
Robert Smile | :)

Richard Andrew x6419-Mar-06 8:17

19-Mar-06 8:17

Basically, when a DLL is linked at compile-time by using the LIB, this embeds information into the EXE file that Windows uses to automatically load the DLL when the process first begins.

So in effect, Windows is calling "LoadLibrary" for you.

There is an excellent explanation on the difference between compile-time linking and dynamic linking in the MSDN library, if you look under "Dlls".

Hope this helps,
Rich

Robert Palma Jr.19-Mar-06 8:28

Robert Palma Jr.

19-Mar-06 8:28

Thanks Rich Smile | :)

Why memcpy not correct!

Hongjun Ge19-Mar-06 7:10

Hongjun Ge

19-Mar-06 7:10

:-OI have a class:

class CTest<br />
{<br />
public:<br />
    char szData1[5];<br />
    char szData2[10];<br />
    char szData3[5];<br />
<br />
    CTest(CString strValue)<br />
    {<br />
        Init();<br />
<br />
        if (strValue.IsEmpty()) {<br />
            return;<br />
        }<br />
<br />
        int nPos = strValue.Find("\n");<br />
        if (nPos != -1) {<br />
            memcpy(szData1, strValue.Left(nPos), sizeof(szData1));<br />
            strValue.Delete(0, nPos + 1);<br />
        } else {<br />
            memcpy(szData1, strValue, sizeof(szData1));<br />
            return;<br />
        }<br />
<br />
        nPos = strValue.Find("\n");<br />
        if (nPos != -1) {<br />
            memcpy(szData2, strValue.Left(nPos), sizeof(szData2));<br />
            strValue.Delete(0, nPos + 1);<br />
        } else {<br />
            memcpy(szData2, strValue, sizeof(szData2));<br />
            return;<br />
        }<br />
<br />
        nPos = strValue.Find("\n");<br />
        if (nPos != -1) {<br />
            memcpy(szData3, strValue.Left(nPos), sizeof(szData3));<br />
            strValue.Delete(0, nPos + 1);<br />
        } else {<br />
            memcpy(szData3, strValue, sizeof(szData3));<br />
            return;<br />
        }<br />
    }<br />
private:<br />
    void Init()<br />
    {<br />
        memset(szData1, 0, sizeof(szData1));<br />
        memset(szData2, 0, sizeof(szData2));<br />
        memset(szData3, 0, sizeof(szData3));<br />
    }<br />
};

I used in MFC application like this
CTest t("1234567890\nabcdefghi\n123456789\n");
TRACE("%s\n", t.szData1);

I got this "12345asdfjpwerpaspo8€gA" that is not my purpose.
Any one can tell why!
Thanks.

Hongjun Ge

-- modified at 2:00 Monday 20th March, 2006

Thanks for all help! I have found solution about this.

class CTest<br />
{<br />
public:<br />
    char szData1[5];<br />
    char szData2[10];<br />
    char szData3[5];<br />
<br />
    CTest(CString strValue)<br />
    {<br />
        Init();<br />
<br />
        if (strValue.IsEmpty()) {<br />
            return;<br />
        }<br />
<br />
        int nPos = strValue.Find("\n");<br />
        if (nPos != -1) {<br />
            memcpy(szData1, strValue.Left(nPos), sizeof(szData1));<br />
            strValue.Delete(0, nPos + 1);<br />
        } else {<br />
            memcpy(szData1, strValue, sizeof(szData1));<br />
            goto Reset;<br />
        }<br />
<br />
        nPos = strValue.Find("\n");<br />
        if (nPos != -1) {<br />
            memcpy(szData2, strValue.Left(nPos), sizeof(szData2));<br />
            strValue.Delete(0, nPos + 1);<br />
        } else {<br />
            memcpy(szData2, strValue, sizeof(szData2));<br />
            goto Reset;<br />
        }<br />
<br />
        nPos = strValue.Find("\n");<br />
        if (nPos != -1) {<br />
            memcpy(szData3, strValue.Left(nPos), sizeof(szData3));<br />
            strValue.Delete(0, nPos + 1);<br />
        } else {<br />
            memcpy(szData3, strValue, sizeof(szData3));<br />
            goto Reset;<br />
        }<br />
Reset:<br />
    szData1[sizeof(szData1) - 1] = '\0';<br />
    szData3[sizeof(szData2) - 1] = '\0';<br />
    szData3[sizeof(szData3) - 1] = '\0';<br />
<br />
    }<br />
private:<br />
    void Init()<br />
    {<br />
        memset(szData1, 0, sizeof(szData1));<br />
        memset(szData2, 0, sizeof(szData2));<br />
        memset(szData3, 0, sizeof(szData3));<br />
    }<br />
};

Richard Andrew x6419-Mar-06 7:26

19-Mar-06 7:26

memcpy(szData1, strValue.Left(nPos), sizeof(szData1));

What happens when sizeof(szData1) is greater than the length of strValue.Left(nPos) ??

Richard Andrew x6419-Mar-06 7:31

19-Mar-06 7:31

memcpy(szData1, strValue.Left(nPos), sizeof(szData1));

This statement seems to be a problem. This statement copies bytes from the CString object itself, not from the string contained within the CString object.

Try:

memcpy(szData1, (LPCSTR)strValue.Left(nPos), sizeof(szData1));

Hongjun Ge19-Mar-06 16:05

Hongjun Ge

19-Mar-06 16:05

Sorry. This method couldn't get the correct result.;P

Hongjun Ge

Richard Andrew x6419-Mar-06 7:41

19-Mar-06 7:41

Sorry for so many posts, but I just realized that you're doing this all wrong.

You should not be copying strings around with the memcpy() function unless you really know what you're doing.

To copy strings from place to place, look up the functions:

strncpy()<br />
strlen()<br />
<br />

and related functions.

bob1697219-Mar-06 8:04

bob16972

19-Mar-06 8:04

I've used memcpy this way for clipboard stuff. As long as the CString is not on the receiving end, the LPCTSTR operator is just fine. If it's on the receiving end you would need to call CString::GetBuffer() and CString::ReleaseBuffer accordingly to get a non-constant string buffer.

Unless I'm missing something obvious right under my nose that is.

Richard Andrew x6419-Mar-06 8:14

19-Mar-06 8:14

I agree. Perhaps I spoke too soon. But I took the assumption that this was a beginner's question - someone not well versed in CStrings and nulls.