Re: How to make flicker free dialog interface? - C / C++ / MFC Discussion Boards

Michael Dunn7-Jul-01 14:18

7-Jul-01 14:18

What do you mean by "it fails"? It doesn't compile? It crashes?

--Mike--
http://home.inreach.com/mdunn/
We've secretly replaced the msdn.microsoft.com servers with Atari 800XLs. Let's see if anyone notices....

Re: CCtrlView for non Windows' controls

7-Jul-01 14:27

I get the "Cannot create blank document" message.

Cheers,

James Millson

How to make flicker free dialog interface?

7-Jul-01 14:07

subj.

I try:

void CTest::OnPaint()
{
CPaintDC dc(this);
CMemDC memdc(&dc);

CRect clip;
memdc.GetClipBox(&clip);
memdc.FillSolidRect(clip, GetSysColor (COLOR_3DLIGHT));

DefWindowProc(WM_PAINT, (WPARAM)memdc->m_hDC, (LPARAM)0);
}

BOOL CTestDlg::OnEraseBkgnd(CDC* pDC)
{
return FALSE;
}

but anyway my *picture control* flickering and after max/min window's size flicks too. Even more when I open any file by CFileDialog my controls aren't repainted.

What's wrong?

Re: How to make flicker free dialog interface?

Michael Dunn7-Jul-01 14:17

Michael Dunn

7-Jul-01 14:17

For a start, handle WM_ERASEBKGND, not WM_PAINT.

--Mike--
http://home.inreach.com/mdunn/
We've secretly replaced the msdn.microsoft.com servers with Atari 800XLs. Let's see if anyone notices....

Re: How to make flicker free dialog interface?

7-Jul-01 14:24

Move all WM_PAINT code to WM_ERASEBKGND? or what?

Re: How to make flicker free dialog interface?

Michael Dunn7-Jul-01 14:29

Michael Dunn

7-Jul-01 14:29

Yes. Since you are painting a custom background color, do it in WM_ERASEBKGND.

--Mike--
http://home.inreach.com/mdunn/
We've secretly replaced the msdn.microsoft.com servers with Atari 800XLs. Let's see if anyone notices....

Re: How to make flicker free dialog interface?

9-Jul-01 3:57

>We've secretly replaced the msdn.microsoft.com servers with Atari 800XLs. Let's see >if anyone notices....

I thought MSDN online seemed a bit quicker than normal!

Re: How to make flicker free dialog interface?

Christian Graus8-Jul-01 2:22

Christian Graus

8-Jul-01 2:22

Micahel is absolutely right, but I'll also point out that when you call CPaintDC the screen is blanked, so if you ever have to draw anything in OnPaint and have trouble with flicker, don't create your PaintDC until you're about to copy the memDC over the top of it. Otherwise you may stop tearing, but you won't do a thing about flicker.

Christian

#include "std_disclaimer.h"

People who love sausage and respect the law should never watch either one being made.

The things that come to those who wait are usually the things left by those who got there first.

Re: How to make flicker free dialog interface?

Tommy H D Svensson18-Sep-01 5:42

Tommy H D Svensson

18-Sep-01 5:42

I don't understand this piece of code...

Where do you get CMemDC from? I don't have it? Frown | :(

Also, why are you not calling BitBlt to eliminate flickering?

Thx,

/Tommy

CString Find

7-Jul-01 12:38

Hello,
Im having some troubles with CString commands.. I have a text file that I am opening with CFile and reading into a CString called strSource... There is a line in the text file like this for example (This is a line in line of text in my "text file" test test) ..

Im trying to search the CString strSource and find "my" then pull the information out of the "" just to the right of "my".. so that I end up with a string with a value of "text file".. in this text file "my" is a unique line of text..

Thanks in advance for you help!
Rob

Rob Jones

Re: CString Find

Michael Dunn7-Jul-01 19:46

Michael Dunn

7-Jul-01 19:46

Nothing terribly difficult about it

int nMyIndex, nFirstQuoteIndex, nSecondQuoteIndex;
 
  nMyIndex = strSource.Find ( _T("my") );
  nFirstQuoteIndex = strSource.Find ( '"', nMyIndex );
  nSecondQuoteIndex = strSource.Find ( '"', nFirstQuoteIndex+1 );
 
CString strFilename = strSource.Mid ( nFirstQuoteIndex+1, nSecondQuoteIndex-nFirstQuoteIndex-1 );

Naturally, error-checking would be a Good Thing to add to this. Smile | :)

--Mike--
http://home.inreach.com/mdunn/
We've secretly replaced the msdn.microsoft.com servers with Atari 800XLs. Let's see if anyone notices....

Re: CString Find

8-Jul-01 5:29

Thank you very much!

Rob

Single application instance

Joe Moldovan7-Jul-01 12:35

Joe Moldovan

7-Jul-01 12:35

Does anyone know of a simple way to ensure that an application has only a single instance running?

When the app is clicked again the running instance should be restored and activated. I am doing all this now with an event and a background thread. It works fine but I seem to recall that there is a simpler way of doing this and I can't find it anywhere.

Apropos, is it possible to send a windows message, like WM_SHOWWINDOW, between applications rather than within an application?

By the way I have no problem getting the PID or the window handle if they are needed for the solution.

Have Fun all.

Re: Single application instance

Tim Deveaux7-Jul-01 12:55

Tim Deveaux

7-Jul-01 12:55

Re Q1:

In 16 bit windows, which was an 'all one process' affair, you could check the hInstance param passed to the entry fn to do this.

Nowadays, the de jure standard is to use shared memory - a named memory mapped file (see CreateFileMapping and MapViewOfFile) that the app creates on startup - if it already exists, exit, perhaps passing control to the first instance.

There was an excellent intro to this stuff in Jeff Prosise's Wicked Code MSJ November 1998.

A background thread approach sounds interesting though.

Re: Single application instance

l a u r e n7-Jul-01 23:00

l a u r e n

7-Jul-01 23:00

and remember we went through the mutex idea here a whiles ago

---
"every year we invent better idiot proof systems and every year they invent better idiots"

Re: Single application instance

Stan Shannon8-Jul-01 1:07

Stan Shannon

8-Jul-01 1:07

This is the way I've done it for about 100 years now, works like a charm :

// Global declaration in CWinApp:
LPCTSTR lpszUniqueClass = _T("MyUnigueClassName");

CMyWinApp::OnInitInstance()
{
// Check status of class name...
if( DoIExist())
{
return( FALSE );
}
.
.
.

// Register our unique class name that we wish to use
WNDCLASS wndcls;
.
.
.
// Specify our own class name for using FindWindow later
wndcls.lpszClassName = lpszUniqueClass;
// Register new class and exit if it fails
if(!AfxRegisterClass(&wndcls))
{
TRACE("Class Registration Failed\n");
return FALSE;
}
.
.
.

}

BOOL CMyWinApp::DoIExist()
{
CWnd *pWndPrev, *pWndChild;

if(( pWndPrev = CWnd::FindWindow(lpszUniqueClass, NULL ) ))
{
if( pWndPrev->IsIconic() )
{
// If iconic, restore the main window
pWndPrev->ShowWindow(SW_RESTORE);
}
// if alive, does it have any popups?
if(( pWndChild = pWndPrev->GetLastActivePopup()) != NULL )
{
pWndChild->SetForegroundWindow();
}
return TRUE;
}
return FALSE;
}

Re: Single application instance

Vu Nguyen7-Dec-01 14:43

Vu Nguyen

7-Dec-01 14:43

Hi!
I tried your example, but failed to get the result. the AfxRegisterClass() always returns false. DO you know why?
I use appWizard to make my dialog base application

Thank You very much
Vu

vucsuf

Re: Single application instance

Vu Nguyen10-Dec-01 10:29

Vu Nguyen

10-Dec-01 10:29

This is where the answer is:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q243953

I found this out after failing to ask for help on this forum. I guess there are more than 1 way to do it. It just happened to me that all the solutions provided by this forum does not work for me at all.

Vu

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q243953

vucsuf

Re: Single application instance

Joe Moldovan8-Jul-01 10:15

Joe Moldovan

8-Jul-01 10:15

Great ideas but just as much work as my original. Pity that hInstance is not atomic across multi-cpu systems but that's asking a lot.

Here is my solution for anyone who is interested. I don't think its very elegant but it works.

At the beginning of xxxApp::InitInstance()look for an event.

BOOL CTestApp::InitInstance()
{
// See if an instance of myself is already running
if (( eDoIExist = OpenEvent( EVENT_ALL_ACCESS, NULL,
"YesIExist" )) != NULL )
{
// Yes. There is someone out there. Wake it up.
SetEvent( eDoIExist );
// And get out
return FALSE;
}

// No. I am the first so set up an event.
eDoIExist = CreateEvent( NULL, TRUE, FALSE, "YesIExist" );

..... Later in the init code when the main window (in my case a dialog) is
..... set up

CTestDlg dlg;
m_pMainWnd = &dlg;

// Create a background thread to look for any other instance and send it
// the main window
::CreateThread( NULL, 0, LookForMyself, m_pMainWnd , 0, NULL );

..... At the end of the same source

DWORD WINAPI LookForMyself( LPVOID lpParameter )
{
// Forever
do
{
WaitForSingleObject( eDoIExist, INFINITE );

// This is just a little flashy way of re-activating the running
// instance
((CDialog *)lpParameter)->ShowWindow( SW_SHOWMINIMIZED );
((CDialog *)lpParameter)->ShowWindow( SW_RESTORE );

// Reset and wait for more intruders
ResetEvent( eDoIExist );

} while ( TRUE );

return 0;
}

Thank you all for your responses!

Re: Single application instance

8-Jul-01 13:21

You could use a mutex to check if you are the first instance, and if not send a app specific message with BroadcastSystemMessage().

(never actually tried it, but i think it should work and be quite a simple solution)

Re: Single application instance

8-Jul-01 13:25

Maybe the mutex is not even needed, sending the app specific message with BroadcastSystemMessage() and the flag BSF_QUERY and checking the retval might do the trick.

Re: Single application instance

9-Jul-01 3:56

Great ideas people! I am going to try all of these just to see what works and what don't.

Re: Single application instance

Bret Faller9-Jul-01 11:27

Bret Faller

9-Jul-01 11:27

If you have a custom mainframe class (RegisterWndClass()) you can just do a FindWindow(clasname, window caption) and then send a message to the HWND that gets returned.

Bret Faller
Odyssey Computing, Inc.

How to create a menu bar in ATL control

Oliver Daniel7-Jul-01 8:59

Oliver Daniel

7-Jul-01 8:59

I'm working on an ATL based control with addition of WTL to support a GUI that will operate within the control's client area. The problem I'm having is getting a regular menu bar to operate within the control. Since ActiveX controls can't support a menu bar, I thought I could use a command bar to contain the menu.

WTL provides a CCommandBarCtrl class that seems to handle this very nicely but the resulting menu bar doesn't handle mouse clicks correctly. Basically the menu bar shows up and each menu highlights as I mouse over them, but they do not respond to mouse clicks. Additonally if I use a keyboard shortcut to select the menu, the application freezes with the menu left flashing. Using Spy++, I can see a continuous flood of WM_NOTIFY messages during the freeze.

I have the command bar operating as a child of a CFrameWindowImpl class which is a child of the control's window. It also integrates with several toolbars within a rebar control. Here's how I create the command bar and setup the menu:

m_CmdBar.Create(m_hWnd, rcDefault, NULL, ATL_SIMPLE_CMDBAR_PANE_STYLE, 0, ATL_IDW_COMMAND_BAR);

m_CmdBar.AttachMenu(LoadMenu(_Module.m_hInst, MAKEINTRESOURCE(IDR_MAINFRAME)));

m_CmdBar.LoadImages(IDR_TBARMAIN);

CreateSimpleReBar(ATL_SIMPLE_REBAR_STYLE);

AddSimpleReBarBand(m_CmdBar, NULL, TRUE);

I believe this works fine in a regular application where the command bar is a child of CMainFrame, but it behaves strangely in my control.

Any help would be appreciated.

- Oliver

Re: How to create a menu bar in ATL control

7-Jul-01 10:10

Have you added REFLECT_NOTIFICATIONS and DEFAULT_REFLECTION_HANDLER to the message maps?

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