|
hey Jason, you are so clear, thx for your reply 
|
|
|
|
|
Hi guys
I want to stop Autorun through my Application.
Thanks in advance
RYK
|
|
|
|
|
VC_RYK wrote: I want to stop Autorun through my Application.
 . Didn't get anything from your query. Can you explain more?
Somethings seem HARD to do, until we know how to do them.
 _AnShUmAn_
|
|
|
|
|
i want to stop AutoPlay of CD as well as USB storage Device by my Application.(as AutoPlay runs while running my Application then AutoPlay will be stoped or canceled)
|
|
|
|
|
Are you not wanting your application to run via the "auto run" feature of the CD? If so, then how are you wanting it to run?
"A good athlete is the result of a good and worthy opponent." - David Crow
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
I think you have to set the key
HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Policies/Explorer/NoDriveAutoRun
to 0xFFFFFFFF
-- modified at 13:16 Wednesday 29th August, 2007
I think you have to restart the PC after that the value is changed,...and it could be a problem remember to restore the old value when close.
So:
you can use the message WM_DEVICECHANGE sended from a driver when a device is inserted.
Russell
|
|
|
|
|
|
Guys,
I have a question concerning blitting to a DirectDraw7 surface using Blt. My objective here is to take the source surface, lets call it XYSurface, and blit it back onto itself, simply rotating it during the blit. Can I do something like this?
<br />
LPDIRECTDRAWSURFACE7 pXYSurface;<br />
RECT rc;<br />
GetClintRect(hDlg, &rc);<br />
<br />
hRet = pXYSurface->Blt(&rc,pXYSurface,&rc,DDBLT_ROTATIONANGLE,&ddbltfx);<br />
<br />
if(hRet != DD_OK)<br />
{<br />
HandleDDErrors(hRet, errorMessage);<br />
MessageBox(NULL,errorMessage,"Error",MB_OK);<br />
return -1;<br />
} <br />
When I do this, hRet is DDERR_SURFACEBUSY. Which reveals that "Access to the surface is refused because the surface is locked by another thread." Is this because I am trying to Blit back on to the source?
Thanks,
Joe
|
|
|
|
|
Hello Friengs,
Yes yes I know there is a function called GetCurrentProcessID(),which returns the process ID of current Process.
But the problem is I am creating to many processes(like notepad ) and i want to know currently on which process the user is working.I tried the above function but it gives me different process Id.Now i dont know what to do.
|
|
|
|
|
AfxBeginThread return the CWinThread object pointer.
And that class contains the member CWinThread::m_nThreadID.
It helps?
Russell
|
|
|
|
|
Gaurang Shah 033 wrote: ...which process the user is working.
Please explain further.
"A good athlete is the result of a good and worthy opponent." - David Crow
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
It's a member of the PROCESS_INFORMATION struct that you passed in a call to CreateProcess()
|
|
|
|
|
Hello
I am trying to use Directshow 9.0 for making an audio player. I use VC++/VS6.0.
I have written a sample grabber filter because I want to do some processing with the audio samples before they are played.
The sample grabber always picks a buffer of a fixed size but I want that size to be configurable. I did some search for the solution and found out that we need to override teh DecideBufferSize method for the output pin. I did that but my DecideBufferSize code is never called. Am not sure where I went wrong.
Can anyone plz guide me how this can be handled.
This is the flow-
I input come from a wav file so I take the output pin from that source. For this output pin I have overridden the DecideBufferSize funtion.
Then this goes to teh input pin of the sample grabber and in the sample grabber callback I do the audio processing.
The output pin of the sample grabber is rendered.
Any help(suggestions or sample code) would be appreciated.
Thanks
|
|
|
|
|
Hello,
I use the following funktion to write log info into a write protected CEdit window for debuging purposes:
void CMyprogDlg::log(LPCTSTR lpszText)
{
long iBegin, iEnd;
CString time;
CString msg;
time = m_CTime_time.Format("%d.%m %H:%M:%S");
msg.Format("[%s] %s", time, lpszText);
iBegin = m_CEdit_log.LineIndex(-1);
iEnd = iBegin + m_CEdit_log.LineLength(iBegin);
m_CEdit_log.SetSel(iBegin, iEnd);
m_CEdit_log.ReplaceSel(msg);
}
for example :
log("blablabla\r\n");
It works well and i'm using it in alot of programs instead of stdout.
The problems is that when i'm trying to put a lot text lines in the window, after a few hundred lines, the function doesn't work as supposed anymore. Instead of creating new lines, the new text replaces the last line.
I'll be very greatfull for any help!
Best Regards,
im79
|
|
|
|
|
Edit controls do have an upper limit (64KB comes to kind). Try this instead.
"A good athlete is the result of a good and worthy opponent." - David Crow
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
You can use RichEdit control to over come this drawback of CEdit control.
|
|
|
|
|
|
Is it possible to disable a network connection and if so how?
|
|
|
|
|
|
Hmm but I need it in a program not a script.
|
|
|
|
|
The WMI classes can be used in code, script, or otherwise.
"A good athlete is the result of a good and worthy opponent." - David Crow
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
Sorry, Yes I have seen it now he hehehe.
Thanks for the help.
|
|
|
|
|
It seems your problem solved.
|
|
|
|
|
In Debug mode it's plotting graph but in release mode does not,
wt might be the reason??
Thanks..
|
|
|
|
|
Do you check that the variables that are being used by you are being initialized properly. A variable may have a different value in the release and in the debug build, causing the differing behavior. And if you go back and see where the value of that variable is set, you will most probably find out that it isn't: You simply forgot to initialize that variable. The reason why the debug build seemed to work is that the debug version of the runtime library initializes dynamic memory and stack variables to known values (in order to track down memory allocation and overwrite errors), while the release version of the runtime library doesn't.
This could very well be just one of the many possible reasons....
Somethings seem HARD to do, until we know how to do them.
 _AnShUmAn_
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
