Thanks Nemanja. That solved my problem.

I think you also have to set the correct font and character set for your edit control. Something like this: CFont fnt; LOGFONT lf; ::ZeroMemory(&lf, sizeof(lf)); lf.lfHeight = 18; lf.lfCharSet = ARABIC_CHARSET; ::lstrcpy(lf.lfFaceName, "System"); fnt.CreateFontIndirect(&lf); GetDlgItem(IDC_EDIT)->SetFont(&fnt); fnt.Detach();

Hi, I couldn't find the Environment tab at the Options part.Are you sure from that? Thanks

I'm not familiar with EVC++, but I supposed you are writing "a native code". You can use CreateWindow. Look in the WM SDK help for class name of the SIP control

http://weseetips.com/2008/06/13/how-to-make-dialogs-for-languages-which-reads-from-right-to-left/[^] Whether this one helps? Regards, Jijo. _____________________________________________________ http://weseetips.com[^] Visual C++ tips and tricks. Updated daily.

You already had an answer to displaying an arabic char - assuming you have the fonts etc etc. But I can't let the line str.Format(_T("%s %c"),str,i); be without jumping on it. You are trying to put the contents of str into str? At best this will crash, at worst it will do very strange things... If you are trying to add new characters to the end of your string, why not just do that? Or just build up a string yourself - it;s a fixed length. A/ CString str; for (wchar_t i = 1500; i < 1800; i++) str += i; B/ wchar_t buf [301]; for (wchar_t i = 0; i < 300; i++) buf [i] = i + 1500; buf [i] = 0; The choice is yours. Iain.

That didn't solve my problem.I think it will be better if I write the code sample. Creating the dialogs as global. pKeyboard = new CKeyboard; pKeyboard->Create(IDD_KEYBOARD,this); ::SetWindowPos(pKeyboard->m_hWnd, HWND_TOPMOST,0,0,cxScreen,2*cyScreen/5, SWP_SHOWWINDOW ); pPhoneEditor = new CPhoneEditor; pPhoneEditor->Create(IDD_PHONEEDITOR,this); pPhoneEditor->SetWindowPos(&wndTop,0,0,cxScreen,cyScreen,SWP_HIDEWINDOW); Is there a problem in this code?

It's a little more complicated than that, although it’s true that MFC's handle maps are thread specific. Here’s how MFC implements CWnd::GetActiveWindow: _AFXWIN_INLINE CWnd* PASCAL CWnd::GetActiveWindow() { return CWnd::FromHandle(::GetActiveWindow()); } Now the following is from MSDN on the ::GetActiveWindow[^] function: The GetActiveWindow function retrieves the window handle to the active window attached to the calling thread's message queue. So ::GetActiveWindow is also thread specific, although you could use the AttachThreadInput[^] to get around this. Steve

The solution is not as straight forward as seems to be. My first approach was to handle WM_SETFOCUS, but it will not work. But I have faced a similar situation my requirement was different. So let me give you the solution, just override OnCommand & check for notification code of WPARAM. :laugh:

Ibrahim, You must have set your CPU of your device. From project->Settings, select WinCE Emulator from drop down or Select StandardSDK from the toolbar option & Rebuild again & then run. But doing so, the program will use standard sdk & compile & not based on Armv4i. For such CPU's got to run via device only, no other alternative. Hope this helps. Thanks Terry

My code is like that; UINT ComThreadEvent1(LPVOID lParam) { CNotepad *dlg = (CNotepad *)lParam; while(HD != NULL) { ::Sleep(500); int index = dlg->events.Find(_T("\r\n"),0); if(index == 0 ) { dlg->thread2->ResumeThread(); dlg->GetEvent(dlg->events.Left(index)); } } return 0; } void CNotepad::GetEvent(CString event) { CString str; if(event.Mid(9,2) == "C0") { str = "Hello"; CMessageBox mBox; mBox.DoModal(); } } Here GetEvent() method is creating Modal Dialog box.How can I send a message to my main UI thread and create a dialog there? Thanks

iayd wrote: if(wnd == dlg1) Use window handles instead of MFC objects to compare. Since MFC window objects are just wrappers around window handles. if( wnd.GetSafeHwnd() == dlg1.GetSafeHwnd() ) ;;//... Nibu thomas Microsoft MVP for VC++ Code must be written to be read, not by the compiler, but by another human being. Programming Blog: http://nibuthomas.wordpress.com

Thank you all.

iayd wrote: char *pbuf = new char(file.GetLength()) file.Read( pbuf,file.GetLength()); In this way occured an error What error? A missing semicolon, perhaps? Did new fail? Did GetLength() fail? Did Read() fail? Be specific. "Love people and use things, not love things and use people." - Unknown "To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

What sort of device is it, and what does it support in the way of IOCTLs? The manufacturer wil know this. To talk to it, as Cedric says, you use CreateFile() DeviceIOControl() etc. Morality is indistinguishable from social proscription

iayd wrote: And If I know the contol code how can I use it? No information about the device = use it a paperweight, depending on how pretty it is. I've had to deal with some odd devices in my time, and most supplier companies are quite good at emailling you the obsolete device pdfs if you ask politely and give them some time. After all, you're not spending money with them at the moment... That's already happened. Or get numbers off it, and google it. You'd be surprised just how much info on odd wacky stuff is floating about out there. Once you have the information, you may even get a COM object that does the work for you, or you'll need WriteFile / ReadFile / DeviceIOControl to talk directly to the driver. Iain. -- Edited once I reread original post! Plz sir... CPallini CPallini abuz drugz, plz plz help urgent.

:)  I don't know about led mike, but I find laughing through the pain to be good therapy. Mark Mark Salsbery Microsoft MVP - Visual C++ :java:

I'm pretty sure MFC hooks the dialog for you.  Why not just derive a class from CFileDialog and call MoveWindow() in a WM_INITDIALOG handler? Mark Mark Salsbery Microsoft MVP - Visual C++ :java: