C / C++ / MFC

Alan Balkany12-Aug-08 7:51

Alan Balkany

12-Aug-08 7:51

Try CWnd::LockWindowUpdate (). http://msdn.microsoft.com/en-us/library/kc4ez6dk(VS.80).aspx[^]

baerten12-Aug-08 21:06

baerten

12-Aug-08 21:06

Thanks for your answer, but it doesn't work.
The modal-Dialog still disappears for a moment and reappears.

If i could freeze the entire Screen, propably directly "the main output device of windows"
So i'm sure that no flickering happens.

The resolution would also resolve some other ugly side-effects during display.

Thanks anyway Smile | :)

Alan Balkany13-Aug-08 4:57

Alan Balkany

13-Aug-08 4:57

OK, what about CWnd::GetDesktopWindow (http://msdn.microsoft.com/en-us/library/bkxb36k8(VS.80).aspx[^]). Then use LockWindowUpdate on the desktop window.

baerten13-Aug-08 22:51

baerten

13-Aug-08 22:51

It resolves not this problem, because after a SetRedraw(FALSE) to GetDesktopWindow the animation of the closing dialog is still drawed (propably only under Vista (because it's a animation))

BUT

It resolves a problem which i try already since over 6 months to resolve.

SO : BIG BIG THANKS Smile | :)

Alan Balkany14-Aug-08 3:35

Alan Balkany

14-Aug-08 3:35

You're welcome!

Bram van Kampen12-Aug-08 9:22

Bram van Kampen

12-Aug-08 9:22

What about ShowWindow(SW_HIDE);
Smile | :)

Bram van Kampen

baerten12-Aug-08 21:08

baerten

12-Aug-08 21:08

Sorry, but i don't understand your answer.

If i would insert a ShowWindow(SW_HIDE); i have also a flickering.
Because the dialog disappears and reappears.

Thanks anyway Smile | :)

Bram van Kampen15-Aug-08 14:21

Bram van Kampen

15-Aug-08 14:21

You said:
( the modal-dialog closes on F3-Key and reopens after a certain work is done it should look like the dialog has never been closed after pressing the F3-Key )

I take it you mean a non-modal Dialog.

Instead of Opening on an event, and Closing with F3, Hide and Unhide the dialog instead. It has the same visual effect as opening and closing, with an awfull lot less overhead. By the way, I take it that your program is single threaded. In that case, no work of any kind is carried out in the other windows while the thread is stuck processing messages in your dialog.(i.e. when your Dialog has the focus).

Smile | :)

Bram van Kampen

File Reading Issue

VC_RYK11-Aug-08 22:10

VC_RYK

11-Aug-08 22:10

Hello Everybody

I am opening a file and reading file till end of file and then close that file and again opening the same file but while reading it goes to EOF so i am not able to read that file again.

can anyboy tell what could be the Problem and how can i read the file again.

Thanks in advance
RYK

Cedric Moonen11-Aug-08 22:20

Cedric Moonen

11-Aug-08 22:20

Post some code.

Cédric Moonen
Software developer

Charting control [v1.4]
OpenGL game tutorial in C++

shaibee11-Aug-08 22:33

shaibee

11-Aug-08 22:33

If you are using the same file object to read the file again, you need to seek the file pointer to beginning of file(BOF), before you read. This is so because you have read to End of File, and when you read again, it tries to read from current position of file pointer. You need to reset the current position to BOF.

I dont know what language are u using but it would be something like

file.Seek(0);

or

filestream.SeekBegin();

or something similar.

Regards,

Its never over !

David Crow12-Aug-08 3:38

David Crow

12-Aug-08 3:38

shaibee wrote:
If you are using the same file object to read the file again, you need to seek the file pointer to beginning of file(BOF), before you read.

The OP said the file was closed before attempting to open and read from it again.

"Love people and use things, not love things and use people." - Unknown

"The brick walls are there for a reason...to stop the people who don't want it badly enough." - Randy Pausch

kbshibukumar11-Aug-08 23:49

kbshibukumar

11-Aug-08 23:49

If you are reading something other than a text file (say, mp3 or mpeg), there can be multiple EOF in the same file. So it is a better idea to first calculate the size of the file and then read byte by byte.
Shibu

CDialog Destroy memory leaks! please help..

Bram van Kampen12-Aug-08 9:26

Bram van Kampen

12-Aug-08 9:26

Use a seek function. If you opened with fopen(...) you use
fseek(F,0,SEEK_SET) to rewind it to the beginning.

Smile | :)

Bram van Kampen

gamja11-Aug-08 21:39

gamja

11-Aug-08 21:39

hi, all

code is,

----------------------------
CDialog * dlg;

while(TRUE)
{
dlg = new MyDialog;
dlg->Create(IDD_DIALOG, this);
Sleep(500);

dlg->DestroyWindow();
Sleep(500);
}
----------------------------

MyDialog is CDialog subcalssing,

MyDialog virtual method override PostNcDestroy()

void MyDialog::PostNcDestroy()
{
delete this;
CDialog::PostNcDestroy();
}

----------------

this code do not always memory leak.

but some time increase using memory. for 4kb... and not decrease using memory

What is problem??

toxcct11-Aug-08 21:47

toxcct

11-Aug-08 21:47

is there some memory allocated in the constructor of the dialog, and not released in the destructor ?

also, how are you mesuring that memory ?

[VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

sashoalm11-Aug-08 21:47

sashoalm

11-Aug-08 21:47

gamja wrote:

void MyDialog::PostNcDestroy()
{
delete this;
CDialog::PostNcDestroy();
}

You are calling a member function of your object *after* deleting it.

There is sufficient light for those who desire to see, and there is sufficient darkness for those of a contrary disposition.
Blaise Pascal

krmed12-Aug-08 2:12

krmed

12-Aug-08 2:12

If you believe you have memory leaks by looking at the Task Manager, you cannot trust the TM to tell you much about memory usage.

The code you've posted is fine, and doesn't leak memory. The Task Manager reports the amount of memory allocated to your process (the working set). When you initially release memory (no longer need it) the task manager does not immediately return that memory to available space - it holds on to it for a while.

You can probably see this if you display your dialog and then close it (you'll see that 4KB in the Task Manager). Next, minimize your application window and watch the task manager, then restore your window.

Hope that helps.

BTW - your PostNCDestroy is fine.

Karl - WK5M
PP-ASEL-IA (N43CS)
PGP Key: 0xDB02E193
PGP Key Fingerprint: 8F06 5A2E 2735 892B 821C 871A 0411 94EA DB02 E193