|
|
BuckBrown wrote: I am NOT a Windows programmer. I come from the UNIX world and everthing Microsoft seems back asswords to me. I have taught myself (with help from people like yourself) just enough MFC programming in the last couple of years to be dangerous, but it has been a real challenge because what experienced Windows programmers take for granted as kindergarten stuff is not really documented very well.
Ah, now that is useful information to aid in our communications! So the COM kernel of windows uses thread local storage for some of it's ?whatever? and therefore requires thread based intialization. Use the OleInitialize()[^] and matching uninitialize() to accomplish this in your thread callbacks when you want to use COM routines in a worker thread.
led mike
|
|
|
|
|
Hi,
Yes, not using the CoInitialize() function at the begining of the thread was the problem with not being able to create an Excel worksheet. Thank you all for your help. I didn't know anything at all about COM before, but now I guess I should bone up on it a little bit.
Buck
|
|
|
|
|
Did you initialize the apartment in the worker thread? You must ALWAYS call CoInitialize[Ex]() in a new thread before making ANY COM-calls...
Always take a look at the HRESULTs given by COM-functions. Then put the error code in the "Error Lookup"-tool that comes with Visual Studio (it's in the tools-menu). It can translate most common COM-errors.
Also, don't forget to call CoUninitialize() in your worker thread when it exits.
Good luck!
--
Verletzen zerfetzen zersetzen zerstören
Doch es darf nicht mir gehören
Ich muss zerstören
|
|
|
|
|
Hi,
Yes, not using the CoInitialize() function at the begining of the thread was the problem with not being able to create an Excel worksheet. Thank you all for your help. I didn't know anything at all about COM before, but now I gues I should bone up on it a little bit.
Buck
|
|
|
|
|
In addition to Joergen's reply, you have to marshal your interface into the new apartment.
Spawning a worker thread and not initializing COM by calling ::CoInitialize[Ex](), is one of the top five mistakes when doing COM. Another one of the top five is using an interface gotten in the primary thread (apartment) without marshalling the interface. If you fail to do this you will get the RPC_E_WRONG_THREAD error.
Usually you marshal an interface by using ::CoMarshalThreadInterfaceInStream() and ::CoGetInterfaceAndReleaseStream().
Have a look here[^].
I think that by about 95% certainty, the above is your problem.
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
|
|
|
|
|
Hi,
Yes, not using the CoInitialize() function at the begining of the thread was the problem with not being able to create an Excel worksheet. Thank you all for your help. I didn't know anything at all about COM before, but now I gues I should bone up on it a little bit.
Buck
|
|
|
|
|
I've created 2 classes each with it's own dialog box in an MDI application
1. commanding class
2. picViewer class
the commanding class has a func load().
where i create a picViewer variable.
<br />
void commanding::load()<br />
{<br />
UpdateData (TRUE);<br />
<br />
FILE *pic, *pic1, *pic2;<br />
picViewer cam1; <br />
pic = fopen("C:\\cv\\16bit.jp2", "rb");<br />
pic1 = fopen("C:\\cv\\nature_50.jp2", "rb");<br />
pic2 = fopen("C:\\cv\\8_8.jp2", "rb");<br />
unsigned int numRead;<br />
<br />
int i = 0;<br />
while(i < 3)<br />
{<br />
if(i == 0)<br />
numRead = fread(buff, sizeof(BYTE), 100000, pic);<br />
else if(i == 1)<br />
numRead = fread(buff, sizeof(BYTE), 100000, pic1);<br />
else<br />
numRead = fread(buff, sizeof(BYTE), 100000, pic2);<br />
cam1.showPicture(buff,numRead);<br />
i++;<br />
Sleep(2000);<br />
}<br />
<br />
fclose(pic);<br />
fclose(pic1);<br />
fclose(pic2);<br />
UpdateData (FALSE);<br />
}<br />
<br />the picViewer class has a func show().
<br />
void picViewer::show(BYTE bfr[], DWORD size)<br />
{<br />
HBITMAP m_bitmap = NULL;<br />
CImage image;<br />
CJpeg2kDecoder imDec;<br />
<br />
image = imDec.Open(bfr, size);<br />
m_bitmap = (HBITMAP)image;<br />
m_nCam1img.SetBitmap(m_bitmap); <br />
}<br />
whenever I run the application i open up both dialog boxes hit run on the commanding dialog box i get an error when i get to "m_nCam1img.SetBitmap(m_bitmap); " which points to:
<br />
_AFXWIN_INLINE HBITMAP CStatic::SetBitmap(HBITMAP hBitmap)<br />
{ ASSERT(::IsWindow(m_hWnd)); return (HBITMAP)::SendMessage(m_hWnd, STM_SETIMAGE, IMAGE_BITMAP, (LPARAM)hBitmap); }<br />
in afxwin2.inl
what does that mean? what am i doing wrong? what would i need to do in order to show a picture in a separate dialog box?
thanks!
Kitty5
|
|
|
|
|
kitty5 wrote: picViewer cam1;
If picViewer is a window or dialog it is never being created therefore the CStatic child window is also never created so IsWindow(m_hWnd) returns false and Asserts during debugging.
led mike
|
|
|
|
|
led mike wrote: kitty5 wrote:
picViewer cam1;
If picViewer is a window or dialog it is never being created therefore the CStatic child window is also never created so IsWindow(m_hWnd) returns false and Asserts during debugging.
picViewer is the class that is related to the picViewer dialog.
I added both
<br />
cam1.Create(IDD_PICVIEWER,0); <br />
cam1.EnableWindow(TRUE);<br />
to my commanding::load() function.
this stops the crashing.
however, no picture is shown in the picViewer dialog box even though i call the show().
<br />
cam1.show(buff,numRead);<br />
Thanks!
-- modified at 14:35 Thursday 1st February, 2007
Kitty5
|
|
|
|
|
kitty5 wrote: picViewer is the class that is related to the picViewer dialog.
I don't know that that means.
In the first code you posted:
void commanding::load()
{
UpdateData (TRUE);
FILE *pic, *pic1, *pic2;
picViewer cam1;
that instance of picViewer is local to that function so it is not related to anything else.
led mike
|
|
|
|
|
led mike wrote: In the first code you posted:
void commanding::load(){UpdateData (TRUE);FILE *pic, *pic1, *pic2;picViewer cam1;
that instance of picViewer is local to that function so it is not related to anything else.
oh... really?!
hmmm. ok then ummm... how would i be able to open up an instance of the picViewer dialog box in the commanding class and be able to update the bitmaps?
i've changed my commanding to:
<br />
int commanding::loadCmdGet3CamData()<br />
{<br />
UpdateData (TRUE);<br />
<br />
FILE *pic, *pic1, *pic2;<br />
picViewer cam1;<br />
pic = fopen("C:\\cv\\16bit.jp2", "rb");<br />
pic1 = fopen("C:\\cv\\nature_50.jp2", "rb");<br />
pic2 = fopen("C:\\cv\\8_8.jp2", "rb");<br />
unsigned int numRead;<br />
cam1.Create(IDD_IMAGEVIEWER,0);<br />
cam1.EnableWindow(TRUE);<br />
int i = 0;<br />
while(i < 3)<br />
{<br />
if(i == 0)<br />
numRead = fread(buff, sizeof(BYTE), 100000, pic);<br />
else if(i == 1)<br />
numRead = fread(buff, sizeof(BYTE), 100000, pic1);<br />
else<br />
numRead = fread(buff, sizeof(BYTE), 100000, pic2);<br />
cam1.showPicture(buff,numRead);<br />
i++;<br />
Sleep(2000);<br />
}<br />
<br />
fclose(pic);<br />
fclose(pic1);<br />
fclose(pic2);<br />
}<br />
thanks,
Kitty5
|
|
|
|
|
What you have posted so far indicates that you lack the basic knowledge required to achieve your goal on purpose. So changing things and trying it might work eventually if you get lucky. There are several good books, there are also some decent sample applications and tutorials available with Visual Studio and/or on msdn.microsoft.com that might help in regards to the fundamental concepts that you are missing. I don't know that I would be capable of providing adequate coverage in a forum.
led mike
|
|
|
|
|
I agree with led mike's response.
I see a misunderstanding of variable scope in your code.
Here's my reply to your other related post:
In your picViewer::show() method:
Your CImage object goes out of scope at the end of the function so it probably destroys the
HBITMAP via its destructor.
Instead of
m_bitmap = (HBITMAP)image;
try
m_bitmap = image.Detach();
and remove this line:
if (m_bitmap) DeleteObject(m_bitmap);
Same with code above: All your variables are local so they no longer exist when the function
ends.
Mark
|
|
|
|
|
Is m_nCam1img on same dialog and when you run m_nCam1img.SetBitmap(m_bitmap); and Is m_nCam1img valid and aslo if you want to load a jpg file you can use of (CImage)
|
|
|
|
|
Hi everyone.
thanks for responding it's been really helpful.
with much reading i figured it out and it all makes sense now.
I added this to my commanding::load():
<br />
ImageViewer *imgViewDlg;<br />
imgViewDlg = new ImageViewer();<br />
imgViewDlg->Create(IDD_IMAGEVIEWER, NULL);<br />
imgViewDlg->SetWindowPos(NULL, 0, 0, 700, 700,SWP_NOMOVE); <br />
imgViewDlg->ShowWindow(SW_SHOW);<br />
& then I call the showImage()
<br />
imgViewDlg->showPicture(buff,numRead);<br />
and this seems like it is working.
now i'm just looking to see if there's a function for "isWindowActive" or something that i can check if the particular dialog box is inactive because I don't nessesarily want to keep updating the pictures if the window is in the background and someother window is on top of it.
thanks!
Kitty5
|
|
|
|
|
|
Good Morning Everyone,
I am using Visual C++ 6.0 MFC. I am writing my first multi-threaded application and I need to be able to use semaphores. In examples that I have looked at they say to declare the semaphore class as CSemaphore cph(1, 2) for example. When I try to declare the semaphore in my class header file the compiler returns with the type of error that you would get if you did not #include a needed header file. Is there a header file that CSemaphore requires to be #included?
Thanks,
Buck
|
|
|
|
|
BuckBrown wrote: Is there a header file that CSemaphore requires to be #included?
They hide that information in the documentation[^]
led mike
|
|
|
|
|
I guess I really don't understand. I read this documentation earlier and thought the idea was something like this -
class CTests : public CWnd
{
// Construction
public:
CTests();
CTemperature* pTemperature;
COutput* pOutput;
CGPIB* pGPIB;
CTabPageSSL* pTabPage;
CSemaphore cph(1, 5);
// Attributes
private:
If I remark out the declaration it compiles fine, if not it does not compile.
Buck
|
|
|
|
|
BuckBrown wrote: I read this documentation earlier
maybe your definition of "reading" is different than mine.
From the documentation:
Requirements
Header: afxmt.h
led mike
|
|
|
|
|
Gee, do I feel stupid now. I was so focused on the body of the document that I didn't even notice the little requirements section. My appologies.
Thanks
|
|
|
|
|
BuckBrown wrote: class CTests : public CWnd
{
// Construction
public:
CTests();
CTemperature* pTemperature;
COutput* pOutput;
CGPIB* pGPIB;
CTabPageSSL* pTabPage;
CSemaphore cph(1, 5);
Doing that in the header file won't compile. The overloaded constructor should be invoked using the constructor of your CTests class:
<code>CTests::CTests() : cph(1, 5) {
If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week
Zac
|
|
|
|
|
Boy that's the truth. That's why I became a microelectronics engineer in the integrated circuit industry (I help develop the silicon that makes us feel stupid).
Thanks for the input
Buck
|
|
|
|
|
Hello,
I am playing around with a DVD-Video API sample which is parently is available online.
When I compile it, it appears that I am a "X11/Xlib.h" file missing. Can anyone tell me where I can get this file, please?
Thank you...
Khoramdin
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
