|
provide the code snippet plz.
... she said you are the perfect stranger she said baby let's keep it like this... Tunnel of Love, Dire Straits.
|
|
|
|
|
The Code snippet is as follows
Here I am using Win32_OperatingSystem Class to access LastBootUpTime property and want to print it in text box, But it gives error.
Although I am able to take other properties of String data type of same class.
So please tell me solution.
IEnumWbemClassObject * pEnumObjectOS = NULL;
HRESULT hResOS;
BSTR strQueryBI = (L"Select * from Win32_OperatingSystem");
BSTR strQLOS = (L"WQL");
hResOS = pWbemServices->ExecQuery(strQLOS, StrQueryOS,WBEM_FLAG_RETURN_IMMEDIATELY,NULL,&pEnumObjectOS);
if(hResOS != S_OK)
{
MessageBox("Could not execute Query");
return;
}
ULONG uCountOS = 1, uReturnedOS;
IWbemClassObject * pClassObjectOS = NULL;
hResOS = pEnumObjectOS->Reset();
if(hResOS != S_OK)
{
MessageBox("Could not Enumerate");
return;
}
hResOS = pEnumObjectOS->Next(WBEM_INFINITE,uCountOS, &pClassObjectOS, &uReturnedOS);
if(hResOS != S_OK)
{
MessageBox("Could not Enumerate");
return;
}
VARIANT vOS;
//CString szStr;
BSTR strClassPropOS = SysAllocString(L"LastBootUpTime");
hResOS = pClassObjectOS->Get(strClassPropOS, 0, &vOS, 0, 0);
if(hResOS != S_OK)
{
MessageBox("Could not Get Value");
return;
}
SysFreeString(strClassPropOS);
_bstr_t bstrPathBIOS = &vOS; //Just to convert BSTR to ANSI
//char* strPath=(char*)bstrPath;
//COleDateTime dateTime(vBIOS.date);
// szStr=dateTime.Format("%H%M%S");
if (SUCCEEDED(hResOS))
SetDlgItemText(IDC_EDIT1,(char*)bstrPathOS);//MessageBox(strPath);
else
MessageBox("Error in getting object");
VariantClear( &vOS );
Thanks.
|
|
|
|
|
rajeevktripathi wrote:
BSTR strQueryBI = (L"Select * from Win32_OperatingSystem");
Am I miss something?? strQueryBI is never executed. You should be doing something like:
<br />
hResOS = pWbemServices->ExecQuery(strQLOS, strQueryBI ,WBEM_FLAG_RETURN_IMMEDIATELY,NULL,&pEnumObjectOS);<br />
Read this[^] if you haven't it may help you.
Marc Soleda.
... she said you are the perfect stranger she said baby let's keep it like this... Tunnel of Love, Dire Straits.
|
|
|
|
|
Hello,
Does:
char* pBuf = new char[nDataSize];
pBuf[nDataSize - 1] = '\0';
help?
If this does not help, could you specify your problem a little bit more clearly? Some code snippets might help also..
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
Hi
I am more specific here:
char* buff = new buff[5];<br />
buff[0] = 'a';<br />
buff[1] = '\0';
buff[2] = 'b';<br />
printf(buff);
if(buff)<br />
delete [] buff;
Any solutions?
Regards
Sreekanth Muralidharan,
Corporate Systems Consultant [Embedded Systems],
INDIA
|
|
|
|
|
Hello,
The '\0' character is a terminater. C runtime functions use that to determine the length of a string. Besides that, you cannot print is, since it is an invisible character. See the ascii table for more inforation.
You can display a space (I think that this is what you want) by doing the following:
buff[0] = 'a';
buff[1] = ' ';
buff[2] = 'b';
This should work.
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
You won't be able to add a 0 to a C-string and still treat it as a C-string. However, there is nothing that prevents you from placing a 0 in a character array. You just can't use traditional C-string functions on it.
Tim Smith
I'm going to patent thought. I have yet to see any prior art.
|
|
|
|
|
for example:
strcpy - bad
memcpy - good
std::strinmg - bad
std::vector<char> - good
Tim Smith
I'm going to patent thought. I have yet to see any prior art.
|
|
|
|
|
Sreekanth Muralidharan wrote:
buffer of character
Instead of Buffer of Character use Buffer of BYTES this will solve your problem 
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
|
Being signed or unsigned has little to do with the problem other than preventing him from calling C-string routines. You can easily place a 0 in a buffer of characters (I've been doing it for years). You just have to be careful which routines and containers you use.
Tim Smith
I'm going to patent thought. I have yet to see any prior art.
|
|
|
|
|
char(acter) = byte = 8 bits
Er zit een korstje op mijn aars.
|
|
|
|
|
Abebe wrote:
char(acter) = byte = 8 bits
Yeap, you are right! I Will discuss with about that later! Stay Tuned
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
|
Hi
There is no need for any head ache there.
Just take it this way and pump it through your serial port. It works !!
char * buff = new char[3];<br />
buff[1] = 0x01;<br />
buff[2] = 0x00;<br />
buff[3] = 0x02;<br />
if(buff)<br />
delete [] buff;
Regards
Sreekanth Muralidharan,
Corporate Systems Consultant [Embedded Systems],
INDIA
|
|
|
|
|
Hi Abebe,
Thanks for your reply.
I know a character is only 1 byte which cannot be accomodated there.
My problem is not that..
See this:
char * buff = new char[5];<br />
buff[0] = 'a';<br />
buff[1] = '\0';
buff[3] = 'c';<br />
printf(buff);
Else any other way to send a 00 through a serial port. I use a serial port monitor to monitor the data from the port. Suppose I have sent this string:
"Code Project"
The monitor should display 00.
Regards
Sreekanth Muralidharan,
Corporate Systems Consultant [Embedded Systems],
INDIA
|
|
|
|
|
'\0' is a terminator not space or EOL.
It is important to keep your terms clear as it leads to more confusion as your work becomes more complex.
If you have a terminator as a member then you must treat it as an array and control the length elsewhere, you cannot use normal string handling functions.
Elaine ![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
The tigress is here 
|
|
|
|
|
To acess a control...
* using GetDlgItem(IDC_) is better or using the control Variable m_Control is better?
regards,
Rookie
|
|
|
|
|
Hello,
It's just a matter of preference. Using the GetDlgItem() involves a lot of ugly typecasts and unnassecary code. Using the m_Control variable looks much more cleaner. I even think that it is slightly faster than the other method, since you already have a CWnd derived object. (Unless you use primitive types or CStrings for managing dialog data.)
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
thanx bob
regards,
Rookie
Installing MFC...2% complete.
|
|
|
|
|
You're welcome
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
as bob said, using GetDlgItem() each time you want to access a control add several function calls to your code that you could avoid.
but of course, using a member variable to store the CWnd* of a control is working unless you initialize it correctly (with... GetDlgItem() )
what i used to do personnaly is having a set of m_p???????? variables in my Dialog classes, that i initialize into OnInitDialog() with a set of GetDlgItem() calls...
TOXCCT >>> GEII power
[toxcct][VisualCalc]
|
|
|
|
|
toxcct wrote:
what i used to do personnaly is having a set of m_p???????? variables in my Dialog classes, that i initialize into OnInitDialog() with a set of GetDlgItem() calls...
You do realize that the return value of GetDlgItem() points to a temporary CWnd object that is only valid for the current Windows message? This means you can't save that return value and use it later, since CWnd object may no longer exist.
Software Zen: delete this;
|
|
|
|
|
IMO depends on the situation. eg: if you have lots of string resources and you need to reset its value it would be a good thing to create all of them consecutively to permit looping from the base one to the last just incresing a counter.
Marc Soleda
... she said you are the perfect stranger she said baby let's keep it like this... Tunnel of Love, Dire Straits.
|
|
|
|
|
nice stuff guys.. it seems that i'd use both the ways according to the need..
thank u so much
regards,
Rookie
Installing MFC...2% complete.
|
|
|
|
|
Hi,
Well you could use either method is correct however, using m_Control has a slight overhead. The reason is that m_Controls are MFC controls while the form has windows controls. So when the form is instantiated the MFC code kicks in and creates the m_Controls. I would prefer this method if I have a lot of interaction with the controls. However if I dont have to interact with the controls or have only to interact with them one time then it is better to use the GetDlgItem method.
Prady
|
|
|
|
|
Overhead you say?
If you use the other method for a lot of controls you typically use not so much (controls in option dialogs for exemple), you create more unnaccesary overhead using more code to initialze and use the controls.
All the unaccessary error checks, function calls are also overhead. The initialization done by MFC is behind the scenes and in GUI applications, the overhead added by MFC doesn't matter very much. So why go through all the fuss of writing pure API code with all the trouble it brings when you can do without?
IMHO, one should write as few lines of Win32 API code for the GUI when he / she uses MFC. This is not only for consistancy, but also saves a lot of troubles.
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
