Click here to Skip to main content

C / C++ / MFC

Re: how to display "ohm sign"?

Alexander ^M.,1-Apr-05 10:01

1-Apr-05 10:01

The console does not support it, and a GUI application will need unicode for that sign because the ANSI converts it to 0x4F and that is 'O'.

Don't try it, just do it! Wink | ;-)

Wink | ;-)

Re: how to display "ohm sign"?

Alexander ^M.,2-Apr-05 1:35

2-Apr-05 1:35

Why did you delete your answer??

The unicode data for L"Ω" is 0xA9 0x03 0x00 0x00.
=> WORD wOhm = 0x03A9;

Don't try it, just do it! Wink | ;-)

Wink | ;-)

Re: how to display "ohm sign"?

vishalmore1-Apr-05 20:09

1-Apr-05 20:09

Hi ds feng,

#ifndef UNICODE
#define UNICODE
#ifdef UNICODE
//ur code for display ohm goes here
#endif

This might solve your problem.

Cheers,
Vishal

Problem with CEdit

Static(x)1-Apr-05 4:13

1-Apr-05 4:13

Hi everybody, i have a problem with CEdit, for example

CString s1="Hello World";
CString s2="This is a Test";

//and we have CEdit variable m_edit
m_edit=s1+"\n"+s2;
as you see i want the result to be

Hello World
This is a Test

but CEdit shows :

Hello World This is a Test

though CEdit is marked in properties as "Multiline"

Can anybody help??

Regards

m0n0

Re: Problem with CEdit

toxcct1-Apr-05 4:27

1-Apr-05 4:27

replace \n with \r\n

it will work... even today (April, 1st) Big Grin | :-D

Big Grin | :-D

ps: is your EditBox declared as MultiLine ?

TOXCCT >>> GEII power
[toxcct][VisualCalc]

Re: Problem with CEdit

ddmcr1-Apr-05 4:30

1-Apr-05 4:30

Thanks it works

m0n0

Re: Problem with CEdit

Michael Dunn1-Apr-05 7:06

1-Apr-05 7:06

For future reference, we have a FAQ:
4.12 How do I create a newline in a multi-line edit control?[^]

--Mike--
LINKS~! Ericahist | 1ClickPicGrabber | CP SearchBar v2.0.2 | C++ Forum FAQ
Strange things are afoot at the U+004B U+20DD

bouli1-Apr-05 2:31

1-Apr-05 2:31

Hi gurus

I'd like to know how I can brutally kill a running thread created via AfxBeginThread?

The core of the function looks like this:

while (!m_dwBytesRead && (nRetries < 2600))<br />
{<br />
m_pReadThread=AfxBeginThread(ReadThread, this, THREAD_PRIORITY_NORMAL);<br />
<br />
nRetries++;<br />
::Sleep(600);<br />
<br />
if (!m_dwBytesRead)<br />
{<br />
// Kill the thread m_pReadThread<br />
}<br />
}

Thanks.

Best regards.

There is no spoon.

Re: Kill a thread

Alexander ^M.,1-Apr-05 2:35

1-Apr-05 2:35

To end the thread, call AfxEndThread from within the thread, or return from the controlling function of the worker thread.

MSDN is your answer.

Don't try it, just do it! Wink | ;-)

Wink | ;-)

Re: Kill a thread

bouli1-Apr-05 2:42

1-Apr-05 2:42

no, not from inside the thread... The creator of the thread, kills its created thread.

<br />
while (!m_dwBytesRead && (nRetries < 2600))<br />
{<br />
	m_pReadThread=AfxBeginThread(ReadThread, this, THREAD_PRIORITY_NORMAL);<br />
		<br />
	nRetries++;<br />
	::Sleep(600);<br />
<br />
	if (!m_dwBytesRead)<br />
	{<br />
		// Kill the thread m_pReadThread<br />
	}<br />
}<br />

There is no spoon.

Re: Kill a thread

toxcct1-Apr-05 2:37

1-Apr-05 2:37

what about SendMessage() ?

TOXCCT >>> GEII power
[toxcct][VisualCalc]

Re: Kill a thread

bouli1-Apr-05 2:43

1-Apr-05 2:43

I wish the creator of the thread kill his created thread:

while (!m_dwBytesRead && (nRetries < 2600))<br />
{<br />
m_pReadThread=AfxBeginThread(ReadThread, this, THREAD_PRIORITY_NORMAL);<br />
<br />
nRetries++;<br />
::Sleep(600);<br />
<br />
if (!m_dwBytesRead)<br />
{<br />
// Kill the thread m_pReadThread<br />
}<br />
}

There is no spoon.

Re: Kill a thread

toxcct1-Apr-05 2:49

1-Apr-05 2:49

ok, i so repost my question :

don't SendMessge() work with the correct argument ? (i don't remember which, but it might be something like WM_KILL or WM_END)... of course, sent to the correct thread, ie. m_pReadThread

TOXCCT >>> GEII power
[toxcct][VisualCalc]

Re: Kill a thread

bouli1-Apr-05 3:10

1-Apr-05 3:10

no, the owner of the thread is not a window. the owner of the thread is a CObject derived class. There must be a way for the owner of the thread to kill its own created thread without condition.

There is no spoon.

Re: Kill a thread

toxcct1-Apr-05 3:19

1-Apr-05 3:19

where did you see that SendMessage() was a member of CWindow or CDialog or i don't even know what else... there's a global one ...

but if you don't want (and you ahve the right to), don't do it ...

TOXCCT >>> GEII power
[toxcct][VisualCalc]

Re: Kill a thread

bouli1-Apr-05 3:25

1-Apr-05 3:25

Hi,

I have explained the purpose of the thread a little bit late. So I repeat the purpose:

the thread just call the ReadFile API. So, if nothing comes, the ReadFile API waits indefinitly. Thus, I can't use OVERLAPPED because it is not supported by the driver. So, I can use only synchronous IOs in my thread. The way I want to handle the ReadFile timeouts (it's not serial IOs) is to use the ReadFile API in a thread and the caller create and destroy the thread after an amount of time while nothing comes. If something comes, the thread finish itself naturally.

I can create the thread, but I don't know how I can destroy the thread FROM the caller. not inside the thread itself.

so, you understand, that if I try to exit FROM the created thread, once it waits for data from the ReadFile, I can wait forever and the thread never exits because it is blocked by the ReadFile API. That's why I need to kill the thread from outside without condition. see what I mean?

thanks.

There is no spoon.

Re: Kill a thread

ThatsAlok1-Apr-05 18:35

1-Apr-05 18:35

Hain Tox!!!
Actually Worker thread don't have any message handlling capability! So how it's going to handle SendMessage(...) Thread.

Same thing is possible with UI threads where you can use PostThreadMessage(..)to send message to the thread!

[Vote One Here, Complete my Survey....]

Alok Gupta
visit me at http://www.thisisalok.tk

"I ~~Think~~ Believe this Will Help"

Re: Kill a thread

eli150219791-Apr-05 3:10

1-Apr-05 3:10

why can't you use global flag and in your child thrad put the code in a loop,like this(Exit is boolian veriable from CTestDlg class):

void CTestDlg::OnTest()
{
    while (!m_dwBytesRead && (nRetries < 2600))
    {
          Exit = false;
          m_pReadThread=AfxBeginThread(ReadThread, this,  THREAD_PRIORITY_NORMAL);

          nRetries++;
          ::Sleep(600);

          if (!m_dwBytesRead)
          {
               Exit = true;// Kill the thread m_pReadThread
          }
    }    
}

UINT ChildThrad(LPVOID lpvoid)
{
    CTestDlg *dlg = (CTestDlg *)lpvoid;
    while(!dlg->Exit)
    {
       //put your child thread code here
    }
    return 0;
}

Re: Kill a thread

bouli1-Apr-05 3:17

1-Apr-05 3:17

the thread just call the ReadFile API. So, if nothing comes, the ReadFile API waits indefinitly. Thus, I can't use OVERLAPPED because it is not supported by the driver. So, I can use only synchronous IOs in my thread. The way I want to handle the ReadFile timeouts (it's not serial IOs) is to use the ReadFile API in a thread and the caller create and destroy the thread after an amount of time while nothing comes. If something comes, the thread finish itself naturally.

I can create the thread, but I don't know how I can destroy the thread FROM the caller. not inside the thread itself.

Best regards.

There is no spoon.

Re: Kill a thread

BadJerry1-Apr-05 3:47

1-Apr-05 3:47

If you want to kill off a thread, you could mention how to do it in VB .... oops sorry I am still in April Fools day mood!
Seriously, you can call (but never advised because of its sheer brutality)
::TerminateThread(m_hThread,0);

Re: Kill a thread

bouli1-Apr-05 3:50

1-Apr-05 3:50

I just wanted that Smile | :)

Smile | :)

at last, you understood my needs Smile | :)

Smile | :)

and now, I have memory leaks, Laugh | :laugh:

Laugh | :laugh:

There is no spoon.

Re: Kill a thread

Blake Miller1-Apr-05 4:55

1-Apr-05 4:55

Memory leaks because you called TerminateThread(), who would have thought.... Just kidding.
But of COURSE you have memory leaks, since your thread did not terminate 'normally'.

You really ARE dealing with a poorly designed driver, aren't you? They should have provided at least a 'is data available' call for you or something. Is there truly no way to set any kind of timeout in case there is no data? Most device drivers will just return that there are no bytes to read instead of hanging your thread up.

Part of your leak might be from the CWinThread object returned from the AfxBeginThread call. When you assssinate your thread, you might want to at least delete the CWinThread object data.

I truly encourage you to seek another driver, or at least a design option that does not force you to continually start and kill threads in this manner.

Good luck!

Re: Kill a thread

bouli1-Apr-05 5:05

1-Apr-05 5:05

Hi,

When I delete the thread from the m_pThread (CWinThread*) it crashes. So, I am using the simple Win32 API function CreateThread and TerminateThread and there is no memory leaks. Laugh | :laugh:

Laugh | :laugh:

Why doing complex as we can do simple?

Indeed, the driver is poorly implemented. It's a USB driver for HP calculators (shipped by HP) and it does not handle correctly the overlapped IO (the system crashes when I use overlapped IOs), if it would have handle them correctly, of course, overlapped IO would have been much more simple. But now, with this brutal algorithm of calling ReadFile in a thread and kill the thread after an amount of time and repeat the operation until something comes works fine now Smile | :)

Smile | :)

But I'm agree that overlapped IO should be the best choice. Of course, using overlapped IOs, is the first idea that came in mind. Wink | ;)

Wink | ;)

There is no spoon.

Re: Kill a thread

bouli1-Apr-05 5:05

1-Apr-05 5:05

Hi,

When I delete the thread from the m_pThread (CWinThread*) it crashes. So, I am using the simple Win32 API function CreateThread and TerminateThread and there is no memory leaks. Laugh | :laugh:

Laugh | :laugh:

Why doing complex as we can do simple?

Indeed, the driver is poorly implemented. It's a USB driver for HP calculators (shipped by HP) and it does not handle correctly the overlapped IO (the system crashes when I use overlapped IOs), if it would have handle them correctly, of course, overlapped IO would have been much more simple. But now, with this brutal algorithm of calling ReadFile in a thread and kill the thread after an amount of time and repeat the operation until something comes works fine now Smile | :)

Smile | :)

But I'm agree that overlapped IO should be the best choice. Of course, using overlapped IOs, is the first idea that came in mind. Wink | ;)

Wink | ;)

Thanks to all of you for the help Smile | :)

Smile | :)

Best regards.

There is no spoon.

Re: Kill a thread

David Crow1-Apr-05 3:56

1-Apr-05 3:56

See here.

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

General News Suggestion Question Bug Answer Joke Praise Rant Admin

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.