That is perhaps the most ugliest way to solve the problem and has many horrible disadvantages ... IT IS OLD SCHOOL HORRIBLE DONT DO IT. Problems you will definitely encounter: 1.) The draw process become slower and slower the more lines you have to draw 2.) As your draw process is contained inside the WM_PAINT message your can't thread it 3.) Your application becomes locked and unresponsive while in the draw process 4.) Every time you resize the window it will redraw all the line database 5.) Every time you move the window order or position it will do an entire redraw Get an old copy of MS_WORD and open a 1MB image file if you want to see what it looks like. Old versions of many Cad programs and Corel draw were practically unusable because they used the above technique and we have long since moved on from it. The correct and more modern way to do this is to create a drawing thread that converts your line database onto a memory DC. That is all the thread does all the time when triggered. The WM_PAINT message simply puts the last finished memory DC from the thread to screen. Usually every database alteration is held so you can also undo-redo function it. The obvious advantages is your program never suffers non responsive or semi locked behavior no matter how complex the drawing gets and the application drawing process does not flash and carry on. Let me know if you get stuck and I will do a quick stub to show you how it works.

You are probably doing it in the wrong place. All painting should be done in response to a WM_PAINT message. Doing it elsewhere means that it will be overwritten the next time the window gets repainted. Note: please put your code (properly indented) in between <pre> tags (use the code link above the edit window) so it is like: if (IsDlgButtonChecked(hDlg, IDC_RADIO1) == BST_CHECKED ) { EndX = LOWORD(lParam); EndY = HIWORD(lParam); SetROP2(hDC, R2\_XORPEN); MoveToEx(hDC, StartX, StartY, NULL); LineTo(hDC, EndX, EndY); IsDrawing = FALSE; } Use the best guess

I'm sorry but we cannot begin to guess what is happening in your program. You need to find out what is happening in your drawing function and whether it is reading the file and processing its content correctly. One of these days I'm going to think of a really clever signature.

:laugh: speaking as ...

enhzflep wrote: the preceding conversation Closed and forgotten. speaking as ...

except for the Express versions AFAIK, they don't offer any choice and always build for "AnyCPU" (unless you start hacking the project files). :) Luc Pattyn [My Articles] Nil Volentibus Arduum

There is no difference in the versions between 32-bit and 64-bit flavors of an OS. Try running the 32-bit application on the 64-bit OS and check if you see the UI properly. If this is working, then the problem is elsewhere in the code. Think about what other changes you have made to port the code to 64-bit. «_Superman_»  _I love work. It gives me something to do between weekends. _Microsoft MVP (Visual C++) Polymorphism in C

sujandasmahapatra wrote: It's crashing with this code (ASSERT failure in appcore.cpp) appcore.cpp is a big place! Whenever you ask for help and say an ASSERT is failing for the love of god paste in the code around the ASSERT statement. Steve

The assertion is telling you the file name and the line number in the file. Have a look there and read the comment which no doubt accompanies the assertion. Steve

It's difficult to suggest anything but it may have something to do with the RepositionBars() calls. You should try a bit of debugging to see what is happening at each step in this function. Unrequited desire is character building. OriginalGriff I'm sitting here giving you a standing ovation - Len Goodman

I have got the problem I have implemented the PrecreateWindow for my view class. just check this code. [code] BOOL CMyView::PreCreateWindow(CREATESTRUCT& cs) { cs.lpszClass = ::AfxRegisterWndClass(CS_HREDRAW | CS_VREDRAW | CS_DBLCLKS | CS_OWNDC,::LoadCursor(NULL, IDC_ARROW), NULL, NULL); cs.style |= WS_CLIPSIBLINGS | WS_CLIPCHILDREN; cs.dwExStyle = WS_EX_CLIENTEDGE; return CView::PreCreateWindow(cs); } [/code] If I remove the first line, i.e cs.lpszClass = ::AfxRegisterWndClass(CS_HREDRAW | CS_VREDRAW | CS_DBLCLKS | CS_OWNDC,::LoadCursor(NULL, IDC_ARROW), NULL, NULL); then my dll window is coming all the times from the client call. But it's flickering . So now please help me what can I do to resolve this. I think some of you must have understood the problem, please help me. Thanks a lot.

thanks a lot it's working now.

You are welcome. Veni, vidi, vici.

Thanks a lot friend. I dint notice that before, now I made it as a member and toolbar is coming . Thanks a lot for help.

sujandasmahapatra wrote: CToolBar toolBar; Shouldn't this be a member variable? "One man's wage rise is another man's price increase." - Harold Wilson "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons "Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous

When you submit the form a new page is loaded. You could make the new page look the same but with your new image embedded in it using only PHP. Or you could load the image inside a frame or iframe by targetting the frame from the form tag. Or you could load the image using Javascript. Also, your PHP code appears to be loading an image using a GD function and then serving it to the browser without changing it at all - unless you are planning to draw on the image or resize it or something, this is very inefficient.