|
a) FindWindow is evil on so many levels. Forget it
b) try to find well-defined application-specific ways to find windows first. The Shell interfaces might contain something for explorer.
c) Use EnumWindows to enumerate all windows. Ask their properties using SendMessageTimeout
d) Never link your expectations about a window to the title. You think a Chinese Explorer has "Windows Explorer" there?
Flirt harder, I'm a Coder
mlog || Agile Programming | doxygen
|
|
|
|
|
peterchen wrote:
You think a Chinese Explorer has "Windows Explorer" there?
I got see what it is ? 
God is Real, unless declared Integer.
|
|
|
|
|
|
What is that written in red ? "Folder"???
God is Real, unless declared Integer.
|
|
|
|
|
The red words should read as "To open that folder (swf)".
The image was found with Google, it is one of illustrations for some operation manual.
That is Windows Explorer of Windows 98, on the title bar there is "Windows Explorer" in Chinese.
I've had a look with my Windows Explorer of WinXP just now. It doesn't show something like "Windows Explorer - Temp" in the current version. Only "Temp" is shown while current folder opened is C:\Temp for example.
Maxwell Chen
|
|
|
|
|
I have developed namespace extension for my company, all these little difference in feature between winxp and win98 caused lot of design problems. 
God is Real, unless declared Integer.
|
|
|
|
|
is there an operator to make a left circular shift directly ???
thanx
shakoosh
|
|
|
|
|
No.
There is however a function, _rotl, and an assembly instruction (Intel added it after the age old joke).
|
|
|
|
|
Hello!
When I use GetActivedocumnet(), happen "Debug Assertion fail"
CObject* p;<br />
ASSERT((p = pMap->LookupPermanent(m_hWnd)) != NULL ||<br />
(p = pMap->LookupTemporary(m_hWnd)) != NULL);<br />
ASSERT((CWnd*)p == this);
but in release mode, no problem.
please tell me about referance or reason.
I waste two day on a reason. 
tool : visual c++ 6.0
|
|
|
|
|
You'll never get assertions in a release build because they're removed by the preprocessor before the compiler compiles the code.
However, you should pay attention to assertions, because they're telling you that something's wrong.
In this particular case, it's telling you that MFC can't find the current window handle value in either its permanent or temporary maps. This is a Bad Thing. The permanent map holds window pointers for windows that you've either created in code from an MFC class, Attached, or subclassed using SubclassWindow. The temporary map holds temporary CWnd objects created by MFC from CWnd::FromHandle, GetDlgItem and many other functions that return a CWnd* (where those functions don't find the handle in the permanent map).
Basically, it means that the window underlying the CFrameWnd object (at a guess) has probably been destroyed or not initialised properly - a NULL m_hWnd is considered a valid CWnd.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
Hey, does anyone know the technique to hold / store / process a log file with a limited size.
Basically i need to know how to have an effient log writing procedure?
|
|
|
|
|
For the limited size:
I found the best solution to simply use two files. If the log file exceeds it's limit, make a backup with a fixed name (overwriting previous backup, if any), and truncate it.
This is a very simple implementation, you always have "enough" past information available, and the log size never exceeds two times the set limit.
Efficiency: Don't use stream operators. (they are painfully slow. I once rewrote an entire logging package for that reason. Further, the syntax is really ugly for logging). I found printf-style fast enough.
I use simple CreateFile/WriteFile, and I *do* Flush at the end of the line. This slows down things - but using the log to debug application crashes, this is invaluable.
If this is not necessary, you could log to a memory buffer, and write out larger chunks.
Flirt harder, I'm a Coder
mlog || Agile Programming | doxygen
|
|
|
|
|
You may want to check the "Platform SDK Documentation" on the MSDN, look for "Event Logging".
Windows provide a mechanism to log events; you may have seen the Event Viewer on the Administrative tools.
Anyway, these are the functions available for this porpoise
Function Description
BackupEventLog Saves the specified event log to a backup file.
ClearEventLog Clears the specified event log, and optionally saves the current copy of the logfile to a backup file.
CloseEventLog Closes a read handle to the specified event log.
DeregisterEventSource Closes a write handle to the specified event log.
GetEventLogInformation Retrieves information about the specified event log.
GetNumberOfEventLogRecords Retrieves the number of records in the specified event log.
GetOldestEventLogRecord Retrieves the absolute record number of the oldest record in the specified event log.
NotifyChangeEventLog Enables an application to receive notification when an event is written to the specified event logfile.
OpenBackupEventLog Opens a handle to a backup event log.
OpenEventLog Opens a handle to an event log.
ReadEventLog Reads a whole number of entries from the specified event log.
RegisterEventSource Retrieves a registered handle to an event log.
ReportEvent Writes an entry at the end of the specified event log.
Fabian
|
|
|
|
|
There are several logging articles on CP including mine.
"We have done so much in the last 2 years, and it doesn't happen by standing around with your finger in your ear, hoping everyone thinks that that's nice." - Donald Rumsfeld
|
|
|
|
|
okay, thanks for the replies all
|
|
|
|
|
seems i have a problem compiling this code
//killprocess.c
#include <windows.h>
#include <tlhelp32.h>
int main(int argc,char *argv[])
{
char szName[100]="something.exe";
TerminateProcess(szName);
return 0;
}
What am I doing wrong?
-Ryan M.
|
|
|
|
|
The process must pass in TerminateProcess() a handle, not a filename. If you want to close a certain applicant, then search for the handle to its main window via FindWindow().
Kuphryn
|
|
|
|
|
TerminateProcess takes a handle to a process and an exit code as parameters so your code as written cannot compile.
You can get a handle to a process using OpenProcess given the Process ID which you can see in Task Manager, or enumerate using the ToolHelp functions CreateToolhelp32Snapshot, Process32First and Process32Next.
Alternatively you could look for a 'kill' program, I think there's one in the Resource kit.
Paul
|
|
|
|
|
http://www.physiology.wisc.edu/ravi/software/killproc/
|
|
|
|
|
I have a dialog based application and I have added a CRichEditCtrl to the dialog using the resource editor (incl. a CRichEditCtrl member variable).
Now I am trying to add text to this control if the user clicks on a button.
I have the following code in the message handler of the button:
m_RTFEdit.SetSel(-1,-1);
m_RTFEdit.ReplaceSel(pszData);
But this seems not to work. In the past I used StreamIn to copy text to a rich edit ctrl but now I want to use ReplaceSel.
Is it possible that the CRichEditCtrl loses the focus and so
ReplaceSel can not work?
Thanks in advance for your help.
|
|
|
|
|
Have you tried
m_RTFEdit.SetSel(0,-1);<br />
m_RTFEdit.ReplaceSel(pszData);
Best regards,
Dominik
_outp(0x64, 0xAD);
and
__asm mov al, 0xAD __asm out 0x64, al
do the same... but what do they do?? 
(doesn't work on NT)
|
|
|
|
|
Yes and I have also tried
GetSel(start, end);
SetSel(end, -1);
But GetSel returns 0,0 so I think the problem is that the RTF ctrl loses the focus(?)
|
|
|
|
|
I want to make a generic file opening program, A simple dialog with one button. The user clicks on it and it launches the file open dialog.When the user selects a file that file is opened and displayed, whether it is a txt or doc or pdf or .... The function WinExec runs executables, but what about opening and displaying any document? I am using VC++ 6.0.Any solutions?
|
|
|
|
|
look up ShellExecute.
If you provide it with a document's file name, Windows will automatically start the corresponding application, as if you'd double-clickj the file in Windows Explorer.
Flirt harder, I'm a Coder
mlog || Agile Programming | doxygen
|
|
|
|
|
WinExec is a holdover from Windows 3.1 and could be removed in the future. Don't use it.
Instead, consider ShellExecuteEx (which can also launch executables). It will use whatever's configured in the Registry, the same as Explorer does.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
