|
You can specify WS_CLIPSIBLINGS in the resource for the dialog; it should be one of the options in the dialog's properties.
My point was that you can't turn WS_CLIPSIBLINGS on and off dynamically.
Software Zen: delete this;
|
|
|
|
|
The resource editor indicates that WS_CLIPSIBLINGS is NOT activated (Properties, Tab Styles, Check button "Clip Siblings" is not checked).
Then why does Spy++ (my code too) indicate that the dialog has WS_CLIPSIBLINGS?
The only way to set/reset that style is the resource editor, or I should create it using Create(...) with or without that style. Is that correct?
|
|
|
|
|
If I have an array of pointers to objects (class objects created using "new"), are the state of those objects preserved? IOW, if certain values existed in an object at the time it was placed in the array, will those values still exist when next the object is accessed from the array?
Several of those objects are created at various times and places in the program, and are subsequently accessed at various times and places as well.
Some of the items in the objects include STL container objects, pointers and other arrays with data in them.
In case someone might think that the array of objects to which I'm referring is an array of objects of the same type, that is not the case. I am referring to an array of pointers to objects (i.e. pointers to various objects of different types which inhabit the array). This, however, is besides the topic of my question which seeks to determine if object state persist.
Thanks for any insight in this matter.
William
Fortes in fide et opere!
|
|
|
|
|
WREY wrote:
If I have an array of pointers to objects (class objects created using "new"), are the state of those objects preserved?
So long as the array hasn't gone out of scope, then yes your objects have been preserved. If they have gone out of scope you have a memory leak, and the memory you are writing / reading to or from may or may not contain your objects - you should assume it doesn't! Sometimes running in debug mode can hide things like that.
If you can keep you head when all about you
Are losing theirs and blaming it on you;
If you can dream - and not make dreams your master;
If you can think - and not make thoughts you aim;
Yours is the Earth and everything that's in it.
Rudyard Kipling
|
|
|
|
|
Scope shouldn't be an issue, because the objects were created using "new", which means you are responsible for deleting them in the end.
Memory leaks are more what I fear.
William
Fortes in fide et opere!
|
|
|
|
|
Since the individual objects pointed to by the array elements are allocated from the heap, they persist until they are deleted. If the array destructor doesn't delete the objects pointed to by its entries, then the objects will survive the array's destruction. (Sounds dramatic, doesn't it  ).
Software Zen: delete this;
|
|
|
|
|
The question is not whether the objects themselves persist, it is whether the "state" of the objects persist.
I know it's my responsibility to call the destructor of each object in the end. So I know the objects are going to persist until I delete them individually. My real concerns are with the state of the objects with regards to the values they contain.
IOW, it is pointless to think every member variable of an object will be "const", or created on the heap, or of 'static' storage type. But when you're dealing with other aspects of C++ like STL, they have their own modus operandi.
William
Fortes in fide et opere!
|
|
|
|
|
WREY wrote:
class objects created using "new"
Because you've created the objects on the heap, they will continue to exist and be valid until destructed, regardless of the disposition of the array containing pointers to them.
/ravi
Let's put "civil" back in "civilization"
Home | Articles | Freeware | Music
ravib@ravib.com
|
|
|
|
|
Can anybody tell me how to create snapshot of MS ACCESS Database in VC++.
Thanks in Advance.
God Knows Better
|
|
|
|
|
Hi, i'm trying to write a winsock layered service provider that filters some UDP traffic and logs it to a file with the ip. The problem is i don't know how to get the ip from in there. I wrote this code but it always gives me 0.0.0.0 as the ip address:
struct sockaddr_in sin;
int err;
int inlen = sizeof(struct sockaddr_in);
if(WSPGetSockName(s, (SOCKADDR *)&sin, &inlen, &err)!=0)
MessageBox(NULL,"Error","lsp",MB_ICONERROR);
char* address;
address = inet_ntoa(sin.sin_addr);
It does not give me an error, it just logs it as 0.0.0.0 
The definition of WSPRecvFrom is as follows:
INT
WSPAPI
WSPRecvFrom(
IN SOCKET s,
IN LPWSABUF lpBuffers,
IN DWORD dwBufferCount,
IN LPDWORD lpNumberOfBytesRecvd,
IN OUT LPDWORD lpFlags,
OUT struct sockaddr FAR * lpFrom,
IN LPINT lpFromlen,
IN LPWSAOVERLAPPED lpOverlapped,
IN LPWSAOVERLAPPED_COMPLETION_ROUTINE lpCompletionRoutine,
IN LPWSATHREADID lpThreadId,
OUT INT FAR *lpErrno
)
Any ideas?
Thanks
Kuniva
--------------------------------------------
|
|
|
|
|
I am trying to grab some data from my database file and display the infromation in my view window. I made a standard scrollview app and added CRecordSet (RecSet) with class wizard. Right now I have this code in my OnDraw fucntion. I am sure there is a better place to put it but I am just playing around at the moment.
long *A;
RecSet *MyRec; // the name of my class is RecSet
MyRec=new RecSet(&m_dbCust); // CDatabase *m_dbCust
MyRec ->GetDefaultConnect();
MyRec ->GetDefaultSQL();
A = &MyRec ->m_Score;
MyRec ->Close();
m_dbCust.Close();
char *B="Hi",Z[100];
pDC ->TextOut(200,200,B);
sprintf(Z,"%d",A);
pDC ->TextOut(400,200,Z);
I know the GetDefaultConnect is working and am assuming he GetdefaultSQL is as well. Do I also need the DoFieldExchange in there as well? Right now I am just trying to grab the data from any row in the Score column of my table and print it to my screen. I am using sprintf because my data is a long type and that is the only way I have got it to convert and print other long numbers to the screen in some testing. Right now it is just printing some random number as far as I can tell. Anybody willing to give me a hint as to what I am missing?
A simpleton trying to get a clue…
|
|
|
|
|
Hello, everyone!
I want to write a process monitor whose function is, when a process is terminated, I can get the process ID of the terminated process and also the application name related with this terminated process.
Are there some materials or sample codes that I can make a reference? Is it a very hard work?
Thanks in advance,
Geo
|
|
|
|
|
|
Thanks, Jörgen buddy!
I can not open the link you provide. 
I have read some materials from MSDN on the topic OpenProcess and a sample program at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/perfmon/base/taking_a_snapshot_and_viewing_processes.asp
But I think it can not meet my demand quite perfectly, because the sample code only takes a snapshot of the processes of the current time. And my purpose is, I can be notified immediately when a process is being killed. Maybe I need some hook on OS?
Can you help?
Best regards,
Geo
|
|
|
|
|
George2 wrote:
I can not open the link you provide.
Sorry about that. I assumed you had the MSDN doc collection installed. :presumptious and embarrased: 
George2 wrote:
And my purpose is, I can be notified immediately when a process is being killed. Maybe I need some hook on OS?
Since you get a HANDLE from OpenProcess you can use wait functions on the handle. They're listed under Platform SDK: DLLs, Processes, and Threads: Wait functions (A bit more neutral reference ).
If you wait for a process, you wait for it to die if I'm not mistaken. I have done this before, although quite a while ago. I do not know where I have the code (probably not still around since I was just playing). But I know this is the way to go.
--
They're out get me, I can't escape cos' they won't let me
They won't forget me, they'll get me in their grip and sweat me
They'll wait me out, and then move in under my skin
They'll make me doubt, they're out to make me let them in
|
|
|
|
|
Thanks, Jörgen buddy!
As you said, "I assumed you had the MSDN doc collection installed. :presumptious and embarrased", what topic or key words should I searched? Maybe I can find one MSDN doc collection from some others machine. Can I find them from Internet?
Can you help?
Best regards,
Geo
|
|
|
|
|
|
Thanks, Jörgen buddy!
Can I use Wait Functions to wait for a process (or being notified when a process is being kill immediately)? I have read this document from the link and I find it can only be used on thread (not process) context.
Best regards,
Geo
|
|
|
|
|
George2 wrote:
I have read this document from the link and I find it can only be used on thread (not process) context.
I'm not sure in what transitions of a process will trigger the wait functions. Threads within that process may trigger them, exceptional errors, etc. But, you can always check the process status using the process functions when the wait function is triggered. You can check if the process is alive or not.
As for thread context, it applies only to the calling thread I believe. Anything with a HANDLE can be monitored with a wait function - may it be a thread, process, file, or what have you.
--
They're out get me, I can't escape cos' they won't let me
They won't forget me, they'll get me in their grip and sweat me
They'll wait me out, and then move in under my skin
They'll make me doubt, they're out to make me let them in
|
|
|
|
|
Thanks, Jörgen buddy!
I will take some time looking the details of this topic. If you have got some sample codes which can meet my purpose, please share them to me.
regards,
Geo
|
|
|
|
|
Hi All
I want to write a program that can serve Dial-up Server
on win98 or winME.
can anyone show me a example or document about this.
thank you so much
|
|
|
|
|
Dear Everybody
I Want to make Dll file But The Exported Functions name have some prefix & post fix.
if my Function name is Myproc its name show az ?abMyproc@@AXDCGFDFFD.
How can I Fix it ?
I'm Sorry For my English too 
tancks.
Iman Ghasrfakhri
|
|
|
|
|
In C++, names are mangled because of their polymorphic nature. Consider the functions
void func(int x) { ... }
void func(float x) { ... }. Clearly the name func is not enough as it is in C. C++ mangles the types involved into the name, resulting in "weird" names as the one you have discovered.
However, functions may be exported with C linkage. This means that you get an unmangled name of that function in the librarys symbol table. It also means that you cannot use that name any longer for polymorphic functions.
You should mark your function with an extern "C" clause. This MSDN link is a good starting point: ms-help://MS.MSDNQTR.2003FEB.1033/vclang/html/_pluslang_Linkage_to_Non.2d.C.2b2b_.Functions.htm[^]
--
They're out get me, I can't escape cos' they won't let me
They won't forget me, they'll get me in their grip and sweat me
They'll wait me out, and then move in under my skin
They'll make me doubt, they're out to make me let them in
|
|
|
|
|
I've got an ATL component that is used to get a Directory listing async for VB clients.
I have 3 interfaces in my Component.
IListing
IDirectory
IFileObject
I listing exposes a method of ExecuteImmediate, and Execute(it creates a thread to do the work).
It then uses the FindFirstFile/FindFirstFile etc to actually do the work.
In this area of the component, I create a CComObject<cdirectory> and store that in the member variable for my component.
Then the hard work is done, and each CComObject<fileobject> as added to the CDirectory object.
All this works perfectly. No leaks, etc.
I then call a property (Contents) to return the IDirectory which is my enumeration of the objects. Also fine.
If I add to the bottom of the ExecuteImmediate/Execute and Event to Fire_Complete(). The system crashes. I've gone through with the debugger, and I can't find anything.
I would really appreciate it if someone could identify any problems with this code(or if I should include some more).
<br />
<br />
DWORD WINAPI SearchFilesFunction2( LPVOID lpParam )<br />
{<br />
SearchFunction(lpParam);<br />
ExitThread(0);<br />
return 0;
<br />
}<br />
<br />
void SearchFunction( LPVOID lpParam )<br />
{<br />
USES_CONVERSION;<br />
CListing2* pListing;<br />
CComBSTR path;<br />
LPTSTR lpsz;<br />
BSTR directoryPath;<br />
BSTR directoryMask;<br />
bool Finished;<br />
<br />
WIN32_FIND_DATA FileFindData; <br />
HANDLE hSearch; <br />
<br />
pListing = (CListing2*)lpParam;<br />
<br />
pListing->m_inProgress = TRUE;<br />
<br />
lpsz = new TCHAR[512];<br />
pListing->get_Directory(&directoryPath);<br />
pListing->get_Mask(&directoryMask);<br />
<br />
path = directoryPath;<br />
path += directoryMask;<br />
<br />
hSearch = FindFirstFile(OLE2CT(path), &FileFindData); <br />
<br />
Finished = FALSE;<br />
<br />
if (hSearch == INVALID_HANDLE_VALUE) <br />
{ <br />
Finished= TRUE;<br />
} <br />
<br />
pListing->pDirectory = new CComObject<CDirectory>;<br />
<br />
while (!Finished) <br />
{ <br />
<br />
CComBSTR fullpath;<br />
BSTR bstr_Filename;<br />
<br />
CFileObject * pFileObject;<br />
pFileObject = new CComObject<CFileObject>;<br />
<br />
_tcscpy( lpsz, FileFindData.cFileName );<br />
<br />
bstr_Filename = SysAllocString(lpsz);<br />
<br />
fullpath = directoryPath;<br />
fullpath += bstr_Filename;<br />
<br />
pFileObject->put_Name(bstr_Filename);<br />
pFileObject->put_Path(directoryPath);<br />
<br />
if (FileFindData.dwFileAttributes & (FILE_ATTRIBUTE_DIRECTORY))<br />
{<br />
pFileObject->put_Type(1);<br />
fullpath += "\\";<br />
}<br />
else<br />
{<br />
pFileObject->put_Type(0);<br />
}<br />
<br />
pFileObject->put_Fullpath(fullpath);<br />
<br />
SysFreeString(bstr_Filename);<br />
<br />
pListing->pDirectory->Add(pFileObject);<br />
<br />
<br />
if (!FindNextFile(hSearch, &FileFindData)) <br />
{<br />
if (GetLastError() == ERROR_NO_MORE_FILES) <br />
{ <br />
Finished= TRUE;<br />
} <br />
else <br />
{ <br />
Finished= TRUE;<br />
} <br />
}<br />
}<br />
<br />
SysFreeString(directoryPath);<br />
SysFreeString(directoryMask);<br />
delete [] lpsz;<br />
<br />
FindClose(hSearch);<br />
pListing->m_inProgress = FALSE;<br />
pListing->Fire_Complete();<br />
}<br />
<br />
STDMETHODIMP CListing2::Execute()<br />
{<br />
<br />
m_inProgress = TRUE;<br />
<br />
hThread = CreateThread( <br />
NULL, <br />
0,<br />
SearchFilesFunction2,<br />
this, <br />
0,<br />
&dwThreadId);<br />
<br />
CloseHandle(hThread);<br />
return S_OK;<br />
}<br />
<br />
<br />
STDMETHODIMP CListing2::ExecuteImmediate()<br />
{<br />
m_inProgress = TRUE;<br />
SearchFunction(this);<br />
m_inProgress = FALSE;<br />
return S_OK;<br />
}<br />
<br />
STDMETHODIMP CListing2::get_Contents(IDirectory **pVal)<br />
{<br />
HRESULT hr;<br />
if (!m_inProgress)<br />
{<br />
<br />
hr = pDirectory->QueryInterface(IID_IDispatch, (void **)pVal); <br />
return S_OK;<br />
}<br />
else<br />
{<br />
return S_FALSE;<br />
}<br />
}<br />
<br />
<br />
|
|
|
|
|
Assuming you are not using free threaded apartments, you are in a canoe on a creek of manure, without paddles. You need to synchronize the apartments by marshalling the pListing interface pointer.
Take a look at Len Holgates excellent article which touches this subject: COM Mailslots - Designing asynchonous COM components for VB[^].
--
They're out get me, I can't escape cos' they won't let me
They won't forget me, they'll get me in their grip and sweat me
They'll wait me out, and then move in under my skin
They'll make me doubt, they're out to make me let them in
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
