C++ dll that can be accessed by Cold Fusion - C / C++ / MFC Discussion Boards

Message Removed

20-Mar-07 13:46

Armond Sarkisian

20-Mar-07 13:46

Message Removed

Re: CString Conversion

Michael Dunn20-Mar-07 15:47

Michael Dunn

20-Mar-07 15:47

See The Complete Guide to C++ Strings, Part II - String Wrapper Classes[^]

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ

Ford, what's this fish doing in my ear?

Application Crash

AAKAra20-Mar-07 9:00

AAKAra

20-Mar-07 9:00

My project is an MFC application; i am running into an application crash when user tries to select an object from the browse window. This does not happened when the user tries to do it with a single click, this happens only when user tries to drag the object a little bit while selecting. I have an option of making a copy of the object when the user tries to drag and drop it, but if the right click and drag is bit fast then the application crashes.
Crash happens at the line DISABLEOLEWARNINGBOXS,

<br />
void CInstanceListCtrl::OnBegindrag(NMHDR* /*pNMHDR*/, LRESULT* pResult) <br />
{<br />
//NM_LISTVIEW* pNMListView = (NM_LISTVIEW*)pNMHDR;<br />
*pResult = 0;<br />
<br />
// If no drop effects are allowed then just exit.<br />
if (0 == m_dropEffectAllowed) return;<br />
<br />
// Create an item list for all of the selected objects.<br />
CPyrItemList* ppil = CreateSelectedItemList (m_fIgnoreClassFoldersInLists);<br />
if (NULL == ppil) return;<br />
<br />
// If we drag the data to another process and it takes a long time<br />
// to complete the drop, it's possible for us to get "server busy"<br />
// dialogs while we're waiting for the other process. So we want<br />
// to turn off those dialogs now.<br />
DISABLEOLEWARNINGBOXS;<br />
<br />
// Create a data source to do the drag-drop and then do the<br />
// drag-drop.<br />
CPyrItemListDataSource DataSource;<br />
DataSource.Create (*ppil);<br />
/*DROPEFFECT dropEffect = */ DataSource.DoDragDrop (m_dropEffectAllowed);<br />
delete ppil;<br />
}<br />

and DISABLEOLEWARNINGBOXS refers to

<br />
#define DISABLEOLEWARNINGBOXS \<br />
COleMessageFilter* pfilter = ::AfxOleGetMessageFilter (); \<br />
if (NULL != pfilter) \<br />
{ \<br />
pfilter->EnableBusyDialog(FALSE); \<br />
pfilter->EnableNotRespondingDialog(FALSE); \<br />
}<br />

the call stack shows

mfc71d.dll!AfxAssertValidObject(const CObject * pOb=0x00000000, const char * lpszFileName=0x7c142b9c, int nLine=33) Line 75 C++
mfc71d.dll!AfxOleGetMessageFilter() Line 33 + 0x15 C++
Util.dll!CInstanceListCtrl::OnBegindrag(tagNMHDR * __formal=0x03f5a9ac, long * pResult=0x03f5a664) Line 2590 + 0x5 C++
mfc71d.dll!_AfxDispatchCmdMsg(CCmdTarget * pTarget=0x03f5c444, unsigned int nID=0, int nCode=65427, void (void)* pfn=0x0072db00, void * pExtra=0x03f5a3d0, unsigned int nSig=57, AFX_CMDHANDLERINFO * pHandlerInfo=0x00000000) Line 119 C++
mfc71d.dll!CCmdTarget::OnCmdMsg(unsigned int nID=0, int nCode=65427, void * pExtra=0x03f5a3d0, AFX_CMDHANDLERINFO * pHandlerInfo=0x00000000) Line 396 + 0x27 C++
mfc71d.dll!CWnd::ReflectChildNotify(unsigned int uMsg=78, unsigned int wParam=1024, long lParam=66431404, long * pResult=0x03f5a664) Line 3251 + 0x23 C++
mfc71d.dll!CWnd::OnChildNotify(unsigned int uMsg=78, unsigned int wParam=1024, long lParam=66431404, long * pResult=0x03f5a664) Line 3205 C++
mfc71d.dll!CListCtrl::OnChildNotify(unsigned int message=78, unsigned int wParam=1024, long lParam=66431404, long * pResult=0x03f5a664) Line 606 + 0x18 C++
mfc71d.dll!CWnd::SendChildNotifyLastMsg(long * pResult=0x03f5a664) Line 3145 C++
mfc71d.dll!CWnd::ReflectLastMsg(HWND__ * hWndChild=0x000307b8, long * pResult=0x03f5a664) Line 3183 C++
mfc71d.dll!CWnd::OnNotify(unsigned int __formal=1024, long lParam=66431404, long * pResult=0x03f5a664) Line 2569 + 0xd C++
SelDlg.dll!0136999e()
mfc71d.dll!CWnd::OnWndMsg(unsigned int message=78, unsigned int wParam=1024, long lParam=66431404, long * pResult=0x03f5a698) Line 1771 + 0x28 C++
mfc71d.dll!CWnd::WindowProc(unsigned int message=78, unsigned int wParam=1024, long lParam=66431404) Line 1745 + 0x1e C++
mfc71d.dll!AfxCallWndProc(CWnd * pWnd=0x03f5b0b4, HWND__ * hWnd=0x000307de, unsigned int nMsg=78, unsigned int wParam=1024, long lParam=66431404) Line 241 + 0x1a C++
mfc71d.dll!AfxWndProc(HWND__ * hWnd=0x000307de, unsigned int nMsg=78, unsigned int wParam=1024, long lParam=66431404) Line 389 C++

Can someone suggest me how to get around this problem?

Anil

Re: Application Crash

PJ Arends20-Mar-07 11:14

PJ Arends

20-Mar-07 11:14

The first thing I would do is change that macro to function. You can then step into the function to better find the source of your error.

You may be right
I may be crazy
-- Billy Joel --

Within you lies the power for good, use it!!!

Re: Application Crash

prasad_som20-Mar-07 18:18

prasad_som

20-Mar-07 18:18

AnilUnni wrote:
COleMessageFilter* pfilter = ::AfxOleGetMessageFilter (); \

First statement in this function is,

ASSERT_VALID(AfxGetThread());

And in your case AfxGetThread is returning NULL pointer. Need to find that cause.

Prasad
Notifier using ATL | Operator new[],delete[][^]

Re: Application Crash

AAKAra21-Mar-07 5:46

AAKAra

21-Mar-07 5:46

Yes Prasad you are correct.
I changed the code so that in case of exception it returns without a crash.
try
{
COleMessageFilter* pfilter = ::AfxOleGetMessageFilter (); \
if (NULL != pfilter) \
{ \
pfilter->EnableBusyDialog(FALSE); \
pfilter->EnableNotRespondingDialog(FALSE); \
}
}
catch(...)
{
return;
}

I guess this should work?

Re: Application Crash

prasad_som21-Mar-07 7:43

prasad_som

21-Mar-07 7:43

If think, instead of this, NULL check would be better option,
ie.

if ( AfxGetThread())//still confused , why this should be NULL in your case
{
COleMessageFilter* pfilter = ::AfxOleGetMessageFilter (); \
if (NULL != pfilter) \
{ \
pfilter->EnableBusyDialog(FALSE); \
pfilter->EnableNotRespondingDialog(FALSE); \
}
}

Because, NULL pointer access will simply cause crash, instead of throwing exception.

Prasad
Notifier using ATL | Operator new[],delete[][^]

C++ dll that can be accessed by Cold Fusion

LCI20-Mar-07 8:50

LCI

20-Mar-07 8:50

Anyone know how to make a C++ dll that Cold Fusion can access?

Re: C++ dll that can be accessed by Cold Fusion

Michael Dunn20-Mar-07 15:50

Michael Dunn

20-Mar-07 15:50

I don't know CF, but most non-C languages require that the functions be exported as C functions with undecorated names, like:

extern "C" __declspec(dllexport) int SomeFunc();

C linkage is the lowest-common-denominator when it comes to exports.

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ

Ford, what's this fish doing in my ear?

automate an already-launched visual studio IDE

ppp00120-Mar-07 8:00

ppp001

20-Mar-07 8:00

Hi,

How can I get the reference of a already launched visual studio IDE
in the Window OS and automate it in my program ?

Thanks

Common Controls 6 and porting from VS2003 to VS2005

Christopher Duncan20-Mar-07 7:02

Christopher Duncan

20-Mar-07 7:02

Hey, guys.

I have a dll that I originally built in VS2003 that uses the new common controls 6 look and feel via jumping through the hoops of the manifest, defining ISOLATION_AWARE_ENABLED and such.

I opened and converted this project in VS2005. Everything compiles, everything works, except that I no longer get the cc6 look and feel. Anyone have any idea what it is about VS2005 that breaks this, and how I can fix it?

Thanks,

Author of
The Career Programmer and Unite the Tribes
www.PracticalStrategyConsulting.com

owner-drawn button

iayd20-Mar-07 6:59

iayd

20-Mar-07 6:59

Hi I am a new learner of visual c++ for a new job.I want to use an owner-drawn button in my application.for example I downloaded CRoundButton2 project from this site but I couldn't use it.my question is that how can I apply this button for the buttons in my project.If someone can explain how can I use them,I will be so glad.(I tried to do what was explained in the project,bu I was not successful.)
Good Bye

(Full name of the project is -> CRoundButton2 - A fancy graphical button)

Re: owner-drawn button

toxcct20-Mar-07 7:12

toxcct

20-Mar-07 7:12

the best place to ask is in the forum at the botton of the article from which you downloaded it.

[VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

Re: owner-drawn button

johny_d20-Mar-07 12:37

johny_d

20-Mar-07 12:37

you will probably need to subclass the item.
here is what you do:
- create a data member for the control you subclass in the class of the owner window
- include the new control header
- change the type of the member

so, you will change

class CMyDialog : public CDialog
{
//blah, blah, blah
CButton m_btn;
};

into

#include "RoundButton2.h"

class CMyDialog : public CDialog
{
//blah, blah, blah
CRoundButton2 m_btn;
};

there are other ways as well, but this looks the best from my POINT of CView

Live long and prosper

johny74656@gmail.com

CImage Woes

VonHagNDaz20-Mar-07 5:32

VonHagNDaz

20-Mar-07 5:32

Hey guys,

I accidently posted this in the wrong forum yesterday, but after the initial flame, i got some suggestions. I figured id repost this in the right forum to see what you guys thought.

Im having a problem with the CImage::GetBits(). Im opening a TIFF file using a CImage object, and i want to take information from this image for use in another function. Here is whats happening.

unsigned BYTE* pBits<br />
chBitBuffer = /*the image*/image->GetBits();

This compiles, and appears to work fine, but after several access violations I went a bit deeper.

image's height = 1179, width = 673, bits per pixel = 32.

So Im assuming that the number of pixels = height * witdth. Number of pixels * 4 = total number of bytes, since each pixel is 4 bytes (32/8).

The problem comes in when I try to access the data returned from GetBits(). The buffer only has a length of 3224 in this example, when my calculations say it should be as long as the number of bytes(3173868).

Any clues to what may be going on here?

I win because I have the most fun in life...

Re: CImage Woes

Dave Calkins20-Mar-07 5:44

Dave Calkins

20-Mar-07 5:44

The individual rows of pixels aren't necessarily right next to each other in memory; chances are there are padding bytes at the end of each row of pixels; Look at the GetBits() and GetPitch() documentation for info on this.

Also, depending on the pitch your pointer may be pointing near the end of the image not the beginning.

When you say, "The buffer only has a length of 3224", which buffer are you referring to? How are you getting this size?

Re: CImage Woes

VonHagNDaz20-Mar-07 5:53

VonHagNDaz

20-Mar-07 5:53

GetPitch() returns a -2692, which mean the DIB is bottom up. this means that the buffer pointer is pointing towards the last row of the image.

the buffer is the bitmap buffer that GetBits() returns the pointer to.
I got the 3224 with a dumb for loop to see when i got the access violation.

for(int i = 0; i < 999999999; i++)
nBits[i] = o;

it broke on i = 3224

I win because I have the most fun in life...

Re: CImage Woes

Mark Salsbery20-Mar-07 8:47

Mark Salsbery

20-Mar-07 8:47

The fact that it faulted at 3224 is arbitrary. There may have been extra bytes allocated for
alignment or efficiency or whatever. That doesn't mean it's ok to read/write past the end of
where the data is supposed to be.

Mark

"Great job, team. Head back to base for debriefing and cocktails."
(Spottswoode "Team America")

Re: CImage Woes

David Crow20-Mar-07 7:24

David Crow

20-Mar-07 7:24

VonHagNDaz wrote:
...but after the initial flame...

You consider this a flame?

"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15

"Judge not by the eye but by the heart." - Native American Proverb

Re: CImage Woes

VonHagNDaz20-Mar-07 8:06

VonHagNDaz

20-Mar-07 8:06

maybe misuse of the term, i was just pointing out that i miss clicked and put the initial question in the wrong forum

I win because I have the most fun in life...

Re: CImage Woes

Mark Salsbery20-Mar-07 8:45

Mark Salsbery

20-Mar-07 8:45

Let 'em move the post if they want to Smile | :)

I kept replying there - I don't know if I helped any.
Mark

"Great job, team. Head back to base for debriefing and cocktails."
(Spottswoode "Team America")

Re: CImage Woes

VonHagNDaz20-Mar-07 9:10

VonHagNDaz

20-Mar-07 9:10

thanks man, your post back in the c++/cli forum did the trick! It was all in the way i was handling the pitch in regard to the pixel buffer. just know that somewhere there is .cpp file with your name quoted!

I win because I have the most fun in life...

Re: CImage Woes

Mark Salsbery20-Mar-07 9:12

Mark Salsbery

20-Mar-07 9:12

Cool!