|
there is:
<br />
long atol(char* str)<br />
It will search through a character string until it reaches a character that is not a number and return the result as a long value.
|
|
|
|
|
atoi() or atol()
farewell goodnight last one out turn out the lights Smashing Pumpkins, Tales of a Scorched Earth
|
|
|
|
|
yeah -- but these aren't overloaded for the STL string -- i am getting conversion errors :<
tim
---------------------------------------
Tim Booher
|
|
|
|
|
use the c_str() function on your object and you will get a const char* to pass into these functions.
|
|
|
|
|
try:
int n = atoi(str.c_str());
farewell goodnight last one out turn out the lights Smashing Pumpkins, Tales of a Scorched Earth
|
|
|
|
|
sweet -- that works great i have:
string convertToMilitary(const string& strTime)
{
// input of form DHHMM i.e. 40112 = 4th day 1:12 pm
string strConverted = "";
int intHour = 0;
intHour = atoi(strTime.substr(1,2).c_str());
if (intHour < 9) intHour += 12;// what is the diff from +=
strConverted = strTime.replace(1,2,intHour);
// output of form DHHMM military (41312)
return strConverted;
}
now i just need to put them back together with all the zeros intact . . . I know i need to change intHour back to string with mask "00"
laters,
tim
---------------------------------------
Tim Booher
|
|
|
|
|
Hello everyone, I'm desperate.
What is going on with this. In debug mode it behaves correctly,
giving the correct output showing the insertions made into the
string:
C:\PleaseHelpMe>cd debug
C:\PleaseHelpMe\Debug>pleasehelpme
~@~bt~@~ <title>The Title of the Document ~@~et~@~ </title>
C:\PleaseHelpMe\Debug>pleasehelpme
~@~bt~@~ <title>The Title of the Document ~@~et~@~ </title>
But in release mode, nothing happens! No changes are made
to the string. Please help! 
C:\PleaseHelpMe\Debug>cd ..
C:\PleaseHelpMe>cd release
C:\PleaseHelpMe\Release>pleasehelpme
<title>The Title of the Document </title>
What is going on? Please help I'm so confused!
Thank you
-Julie
// PleaseHelpMe.cpp : Defines the entry point for the console application.
//
#include "stdafx.h"
#include <afx.h>
static TCHAR g_szBeginTitle[] = "~@~bt~@~";
static TCHAR g_szEndTitle[] = "~@~et~@~";
void InsertCode( TCHAR*& pszBuffer, TCHAR* pszKeyWord, bool& bLineChanged )
{
if ( pszBuffer )
{
*pszBuffer = ' ';
pszBuffer++;
while (*pszBuffer != '\0' && *pszKeyWord != '\0' )
{
*pszBuffer = *pszKeyWord;
pszBuffer++;
pszKeyWord++;
}
if ( pszBuffer )
{
*pszBuffer = ' ';
pszBuffer++;
}
bLineChanged = true;
}
}
void MarkHTMLSignificance( CString& strLine )
{
CString strNewLine;
int nLen = strLine.GetLength() + 2;
TCHAR* pszSource = strLine.GetBuffer( nLen );
TCHAR* pszResult = strNewLine.GetBuffer( nLen * 8 );
bool bLineChanged = false;
while (*pszSource != '\0')
{
if ( *pszSource == '<' )
{
LPTSTR pszTest = pszSource + 1;
switch ( *pszTest )
{
case 't': // possibly title
case 'T':
if ( _tcsnicmp( pszTest, _T("title"), 5 ) == 0 )
InsertCode( pszResult, g_szBeginTitle, bLineChanged );
break;
case '/':
pszTest++;
switch( *pszTest )
{
case 't':
case 'T':
if ( _tcsnicmp( pszTest, _T("title"), 5 ) == 0 )
InsertCode( pszResult, g_szEndTitle, bLineChanged );
break;
} // end switch on slash
} // end switch on t, h, b, slash
} // end if < found
*pszResult = *pszSource;
pszSource++;
pszResult++;
} // end while *pszSource != '\0'
*pszResult = *pszSource; // null terminate!!!
strLine.ReleaseBuffer();
strNewLine.ReleaseBuffer();
if ( bLineChanged )
strLine = strNewLine;
}
int main(int argc, char* argv[])
{
CString strHTML = " <title>The Title of the Document</title> \n";
MarkHTMLSignificance( strHTML );
printf( strHTML );
return 0;
}
|
|
|
|
|
Please, when you post code that has < and > characters in it, either manually replace them with < and >, use a program that will do it for you, or check the Display this message as-is (no HTML) checkbox when posting. It's very hard to read otherwise. Using the <pre> tag around your code (for indentation) would also be nice.
Ok, here's one problem:
void MarkHTMLSignificance( CString& strLine )
{
...
TCHAR* pszResult = strNewLine.GetBuffer( nLen * 8 );
...
InsertCode( pszResult, g_szBeginTitle, bLineChanged );
...
}
void InsertCode( TCHAR*& pszBuffer, TCHAR* pszKeyWord, bool& bLineChanged )
{
...
while (*pszBuffer != '\0' && *pszKeyWord != '\0' )
...
}
A buffer is allocated, but no initialization other than copying in the original string is performed. Looking for a NULL terminator is not a good idea; you should instead pass in a length count, and check using that.
I should also probably mention the CString::Replace() method...
farewell goodnight last one out turn out the lights Smashing Pumpkins, Tales of a Scorched Earth
|
|
|
|
|
Okay, I fixed the display of the message... thanks
But see, I don't to replace anything, I just want to insert
some characters at a specified place. And I want to go fast, cause
I have to process a lot of text, so that's why I'm trying to use
pointers instead of CString operations. And it works fine in debug
mode, that is what is killing me.
I even tried turning off all release mode optimizations, and still
nothing!
Even if I set strNewLine to "", that does not make any difference.
Its like the release mode version doesn't like the fact that I'm
passing a TCHAR* by reference to InsertCode. But why?
Sigh... I was hoping to have this program done by Monday, but
its not looking good because of this... :P
Thanks for any more thoughts ....
|
|
|
|
|
Well, your desire for speed is certainly understandable. But it might be best to start out writing code that works, and then optimize it.
Anyway, as i said above: i doubt the CString buffer is being initialized. This means that in debug mode, it will contain 0xdbdbdbdb (or some such filler meant to identify uninialized memory) but in release, it might be anything.
Do the following:
get rid of this line
if ( pszBuffer )
in this line, get rid of the bold part
while (*pszBuffer != '\0' && *pszKeyWord != '\0' )
You'll then be rather unsafe, but the program should work if i'm right. A correct solution would be to pass in the length of the buffer.
farewell goodnight last one out turn out the lights Smashing Pumpkins, Tales of a Scorched Earth
|
|
|
|
|
You are a genius. That actually worked. I can't believe it.
That is pretty weird.
I'm stunned because I thought that and have always heard that
CStrings were initialized to empty in their constructor.
But I mean, if I do this
CString strLine;
or
CString strLine = "";
Shouldn't the string be initalized to an empty string???
Hmmm...
-Julie
|
|
|
|
|
I still don't understand why that works:
void MyFunct( LPCTSTR& pszBuffer )
{
if ( pszBuffer )
do_something();
}
...
CString strLine;
LPCTSTR szBuffer = strLine.GetBuffer( 100 );
MyFunct( szBuffer )
....
How could szBuffer be null in release mode? If its pointing to strLine's
buffer, its definitely pointing to something non-null.
why does this work?
I'm mystified..
Thanks,
-Julie
|
|
|
|
|
Life is Full of Suprises
VC++ in debug mode assignes non-NULL values to newly allocated memory as a debug helper. This explains why it works in debug.
pszBuffer should not be NULL. I'm not sure why i told you to get rid of the line that checked for that. (not sure why i'm still on CP at 12:30AM either... great, another addiction)
However, the data pointed to by pszBuffer might easily be NULL. Especially the first character, since this would be the NULL terminator on an emtpy string. Internally, CStrings maintain a length counter, so the actual databuffer can be any size. The NULL terminator is strictly for the convenience of C-style string handling routines that need to access the CString. Keep in mind how the standard C library functions work: strcpy() does not require a length specifier, but is a danger spot for buffer overruns if you are not careful, since it does not (and cannot) check that the destination buffer is large enough to hold the source string. strncpy() does require a length specifier, and uses that to operate safely.
This is why using a string class instead of raw C-style strings is nice; constantly having to make your code aware of the total size of buffers gets old in a hurry.
Anyway, sorry you have to be working on the weekend; good luck on your project!
farewell goodnight last one out turn out the lights Smashing Pumpkins, Tales of a Scorched Earth
|
|
|
|
|
Thanks, you have totally saved my life. I was full-on panicking
earlier this evening.  whew! 
|
|
|
|
|
I think I get it.
The content of the pointer could be anything, as you said.
Even though I said I wanted to allocate a certain amount
for a buffer using GetBuffer, the contents of the buffer
could be anything - including '\0', but it wouldn't be a '\0'
that I had asked for or put in there. It would just be random
memory. Oh jeez. weird. ok.
Thanks again,
-Julie
|
|
|
|
|
Hello,
I have a subclass from CDialogBar. I try tu put a IP control in it, but i can´t get the bytes in that control.
I see that happens not only with this control, it happens with any control that don´t be a edit...
What happens?
Thanks Codeprojects...
UI
|
|
|
|
|
Can you post some code? I've used CDialogBars quite a bit, and have never experienced the problems you are talking about.
------------------------
Derek Waters
derek@lj-oz.com
|
|
|
|
|
Hi everyone. I have some code which centers a series of buttons on a dialog, which is in OnSize(). Problem I have is, as the user resizes the control, the buttons are drawn twice (?), and there are "artifacts" of the original draw are still there. If the window is minimized and brought back up again, the buttons draw properly and the "artifacts" are gone. The buttons do center and adjust properly as the window is resized, but leave those "artifacts" for some reason. It doesn't happen when the window is maximized and normalized, but do occur when the user drags the window frame and resizes that way.
I am also using Paul Wendt's CControlPos class which is found on Codeproject, which moves all the other controls (I had to move the buttons manually to achieve the centering with a series of buttons).
Anyone have any ideas? Any help is greatly appreciated!
<br />
void CDlgMain::OnSize(UINT nType, int cx, int cy) <br />
{<br />
CDialog::OnSize(nType, cx, cy);<br />
<br />
CRect rcButtonRect;<br />
<br />
if(::IsWindow(GetDlgItem(IDC_BTN_ADD)->GetSafeHwnd()))<br />
{<br />
<br />
bool bDrawAgain = true;<br />
<br />
GetDlgItem(IDC_BTN_ADD)->MoveWindow(rcButtonRect, bDrawAgain);<br />
<br />
rcButtonRect.left = ((cx - iParentWidth)/2) + iButtonLeft;<br />
rcButtonRect.right = rcButtonRect.left + iButtonWidth;<br />
GetDlgItem(IDC_BTN_EDIT)->MoveWindow(rcButtonRect, bDrawAgain);<br />
<br />
rcButtonRect.left = ((cx - iParentWidth)/2) + iButtonLeft;<br />
rcButtonRect.right = rcButtonRect.left + iButtonWidth;<br />
GetDlgItem(IDC_BTN_DELETE)->MoveWindow(rcButtonRect, bDrawAgain);<br />
<br />
iButtonLeft = 391;<br />
rcButtonRect.left = ((cx - iParentWidth)/2) + iButtonLeft;<br />
rcButtonRect.right = rcButtonRect.left + iButtonWidth;<br />
GetDlgItem(IDC_BTN_COPY)->MoveWindow(rcButtonRect, bDrawAgain);<br />
}<br />
<br />
m_cControlPos.MoveControls();<br />
}<br />
|
|
|
|
|
Is WS_CLIPCHILDREN set for the dialog?
Maybe calling CDialog::OnSize(nType, cx, cy); after moving the controls would work.
farewell goodnight last one out turn out the lights Smashing Pumpkins, Tales of a Scorched Earth
|
|
|
|
|
I tried doing both, with no luck  It still leaves junk behind when the user drags on the window frame
|
|
|
|
|
well, you could also pass in FALSE to all the MoveWindow() calls, then follow everything with Invalidate(TRUE). It'll flicker a bit, but should look ok.
farewell goodnight last one out turn out the lights Smashing Pumpkins, Tales of a Scorched Earth
|
|
|
|
|
I've also seen this problem when resizing static picture controls (eg: frame borders). Try invalidating and updating the dialog at the end of the repositioning.
void CDlgMain::OnSize(UINT nType, int cx, int cy)
{
CDialog::OnSize(nType, cx, cy);
....
Invalidate();
UpdateWindow();
}/ravi
"There is always one more bug..."
http://www.ravib.com
ravib@ravib.com
|
|
|
|
|
That worked great! Thanks for the help!
|
|
|
|
|
i am trying to write a tictactoe game in VC++ but i dont know how to organize it and whats the best way to do it. i am planing to use Bitmap graphics and beneath it use a grid to find out which one the user clicks. and i am planing to use recursion to implement it but i dont know if thats the efficient way to do it. can anyone help me. i am not good in designing? can someone give me an advice on whats the best way to do it?
|
|
|
|
|
This is your homework, isn't it.
Here's what i'd do to get started:
use the VS wizards to create a dialog based app. Delete all controls from the dialog. Implement an OnPaint() handler that draws your board. Handle mouse messages to respond to player actions. Use a separate class to implement game logic.
There are many ways to implement a tic-tak-toe game; just use whatever makes the most sense to you. If you have a specific question, i'm sure you'll get plenty of answers to it.
Have Fun!
farewell goodnight last one out turn out the lights Smashing Pumpkins, Tales of a Scorched Earth
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
