C / C++ / MFC

Re: After AfxBeginthread...

17-Jul-06 2:42

Why aren't you using the value passed to DllMain()?

"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank

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

Re: HINSTANCE for DLL

Manjunath S17-Jul-06 3:35

Manjunath S

17-Jul-06 3:35

Hi all,
I used the hinstance passed in the dll main,And i used it to create dialog model using createdialog . But in that dialog i have static control(having text "driver is loading please wait"),this static text is not displaying . but it display after i returned from that DLL function...

Manjunath S
GESL
Bangalore

After AfxBeginthread...

Smith#17-Jul-06 1:18

Smith#

17-Jul-06 1:18

I start threads using AfxBeginThread like :

<br />
AfxBeginThread(myproc,(LPVOID)data);<br />
<br />
UINT myproc(LPVOID lparam)<br />
{<br />
  do<br />
   {<br />
<br />
   }while;<br />
   <br />
 return(0); ---------> is this enough to close the thread. ? <br />
}<br />

I read if p_AutoDelete in a CWinThread object is set to true(which is it's default) , the thread gets deleted automatically. But I'm not assigning my AfxBegin call to a CWinThread object, But still do you think it'll get deleted automatically? valid suggestions please..
Thanks,

Unsure | :~

see me17-Jul-06 1:54

see me

17-Jul-06 1:54

hi,

I thing here in ur case the thread gets deleted while returning from the thread function

Dream bigger... Do bigger...Expect smaller
aji

Re: After AfxBeginthread...

ThatsAlok17-Jul-06 2:17

ThatsAlok

17-Jul-06 2:17

Meat Loaf wrote:
e thread gets deleted automatically.

that will do

"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow

cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
Support CRY- Child Relief and You

Re: After AfxBeginthread...

tanvon malik17-Jul-06 2:49

tanvon malik

17-Jul-06 2:49

Yes your thread will go to death automatically. because a thread created with a AfxBeginThread() call in MFC is always a CWinThread .

Happy programming keep asking.
I am the brain behind...

How get a list of LogSources ?

fx920017-Jul-06 0:22

fx9200

17-Jul-06 0:22

HELLO,
Now i can read and write all events in any log source (Application,System...)
i can catch each event logging in a specified log source.
the problem is that i want to cach any event in any log source.

this is the proc of catch:

BOOL notifyChange(LPCTSTR logSource)
{
BOOL bSuccess;
HANDLE hEventLog, hEvent;
DWORD dwWaitResult;

hEventLog = OpenEventLog(NULL, // local machine
logSource); // event log source name
if (hEventLog == NULL)
{
printf("Could not open event log.");
return FALSE;
}

hEvent = CreateEvent(NULL, // default security attributes
FALSE, // no manual reset
FALSE, // create as not signaled
NULL); // no event name

NotifyChangeEventLog(hEventLog, hEvent);

dwWaitResult = WaitForSingleObject(hEvent, INFINITE);
if (dwWaitResult == WAIT_FAILED)
bSuccess = FALSE;
else bSuccess = TRUE;

CloseHandle(hEvent);
CloseEventLog(hEventLog);
return bSuccess;
}

is this the correct/best way to set file size? [modified]

George_George17-Jul-06 0:09

17-Jul-06 0:09

Hello everyone,

I have verified that the following approach works to set the size of a file (newly created file) to be 100 bytes, but I am not sure whether it is the correct/best way to have a maximum portability (I need to write code on both Windows and Linux).

Could anyone give me any comments?

<br />
#include "fcntl.h"<br />
#include "sys/types.h"<br />
#include "sys/stat.h"<br />
#include "io.h"<br />
#include "stdio.h"<br />
<br />
int main()<br />
{<br />
	FILE* file = fopen ("foo123", "w+");<br />
	<br />
	fseek (file, 99, SEEK_SET);<br />
<br />
	fprintf (file, "x");<br />
<br />
	fclose (file);<br />
<br />
	return 0;<br />
}<br />

thanks in advance,
George

-- modified at 6:11 Monday 17th July, 2006

David Crow17-Jul-06 2:44

17-Jul-06 2:44

It's probably a lot more portable than SetEndOfFile(). Wink | ;)

"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank

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

George_George17-Jul-06 3:05

17-Jul-06 3:05

Thank you DavidCrow!

What do you mean SetEndOfFile()? Is there a method called SetEndOfFile() in C?

regards,
George

David Crow17-Jul-06 3:49

17-Jul-06 3:49

George_George wrote:
Is there a method called SetEndOfFile() in C?

There's a function called SetEndOfFile().

"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank

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

George_George17-Jul-06 4:08

17-Jul-06 4:08

Thank you DavidCrow!

Why my method is better than SetEndOfFile()?

regards,
George

David Crow17-Jul-06 4:14

17-Jul-06 4:14

George_George wrote:
Why my method is better than SetEndOfFile()?

You wanted portability, didn't you?

"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank

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

George_George17-Jul-06 20:49

17-Jul-06 20:49

Thank you DavidCrow!

Yes, I mean why SetEndOfFile() has worse portability?

regards,
George

David Crow18-Jul-06 2:34

18-Jul-06 2:34

George_George wrote:
...why SetEndOfFile() has worse portability?

It's only for a Windows platform.

"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank

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

George_George18-Jul-06 22:26

18-Jul-06 22:26

Thank you DavidCrow!

regards,
George

earl17-Jul-06 4:57

earl

17-Jul-06 4:57

There's two ways to get portability; the first is to use a common API and test it enough to make sure it works the same way on both systems; the second is to do such:

int main(int argc, char** argv)
{
  #if defined(WINDOWS)
  //put windows code here

  #elif defined(LINUX)
  //code that does the same thing in linux
  #endif

  return 0;
}

The former tends to make for much more readable code... at least IMO.

earl

George_George17-Jul-06 20:51

17-Jul-06 20:51

Thank you earl!

Your sample is only the general principle to develop portable code. In my case, to set the length of a file, is my method showed above has good portability? Do you have any better ideas or any comments?

regards,
George

Re: is this the correct/best way to set file size? [modified]

earl18-Jul-06 6:40

earl

18-Jul-06 6:40

Why do you need the file to be 100b?

I imagine your example should work, unless there are examples of sparse filesystems in use? I doubt it, but I don't keep up with the various file systems in use under linux.

Alternatively, you could just fwrite 100b of zeroes...

unsigned char buff[100];
memset(buff, 0x0, 100 * sizeof(unsigned char));

fwrite(buff, sizeof(unsigned char), 100, fp);

earl

George_George18-Jul-06 22:28

18-Jul-06 22:28

Thank you earl!

Your method is using more memory compared with my method -- 100 more bytes for the local char array. Agree?

regards,
George

-- modified at 4:28 Wednesday 19th July, 2006

earl19-Jul-06 3:14

earl

19-Jul-06 3:14

Sure, but who cares? As written it'll be allocated on the stack and disappear after the function is finished. You also could call fwrite 100 times on a single byte, if you're working in a space where 100b matters.

earl

George_George19-Jul-06 20:34