|
At a guess, since you did not provide the relevant code, you are initializing counter60 to 0 every time on your button click and incrementing it to 1.
And this is C++/CLI and should have been posted in the appropriate forum.
|
|
|
|
|
You need to put your counter variable in the class; or make it a static variable.
Now, I assume you re-create the variable each time you click on the button.
(in c++, pseudo-ish code....)
class YourClass
{
YourClass();
int m_Counter;
void OnButtonClick();
}
YourClass::YourClass () : m_Counter(0)
{
}
void YourClass::OnButtonClick()
{
m_Counter++;
Counter->Text = System::Convert::ToString(counter60);
}
Nihil obstat
|
|
|
|
|
How do you mean "Re-create" ?
I am kind of a rookie.
I use Visual c++ 2010.
|
|
|
|
|
Do you have to call an updatedata() type func like in MFC to refresh the GUI?
If not debug it, it shoud be 61 not 1. Step into the converttostring and make sure you get the right string back, then step into the ->Text func and make sure its being set.
==============================
Nothing to say.
|
|
|
|
|
> This < should help.
"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan
That's what machines are for.
Got a problem?
Sleep on it.
|
|
|
|
|
Hi,
I have created a property sheet. On that 3 Tab controls and three pages have been added.
When I use new larger Images for Tab controls, then it didn't display full Image, it accepts the older size of the Image and display new Image in that area only.
How to resize tab controls in mfc.
Any help will be appreciated.
Regards,
Mbatra
modified 16-Apr-13 7:48am.
|
|
|
|
|
|
I am not sure what you really want but u can use
MoveWindow()
Function .
Moves,resize window as per co-ordinate. 
|
|
|
|
|
do you know how to assign strings in c program?please answer me.
|
|
|
|
|
Yes I do know. Now, what is your question?
Use the best guess
|
|
|
|
|
"assign strings in C"
A Question for you. Does C language support Object Oriented Concepts?
|
|
|
|
|
Objective-C does.
Standard C, no.
"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan
That's what machines are for.
Got a problem?
Sleep on it.
|
|
|
|
|
|
No sign of ++ in the OP heading. That's why I didn't mention it.
"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan
That's what machines are for.
Got a problem?
Sleep on it.
|
|
|
|
|
const char* string = "string";
If you want a string that is not constant, that would be assigned differently, and the answer would depend on whether you mean "assign memory space" or "assign the characters forming the string" when you say "assign", as these are two separate activities in C.
What do you want to know? What have you tried? What books and/or articles have you read, and what is it you do not understand? Who was that masked stranger?
|
|
|
|
|
Here is wide character string version for international users.
const wchar_t* string = "string";
Unicode/MBCS gets very messy developing on Windows, dependent on whether UNICODE is defined at compile time.
see this article for a comprehensive explanation.
What-are-TCHAR-WCHAR-LPSTR-LPWSTR-LPCTSTR-etc?
"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan
That's what machines are for.
Got a problem?
Sleep on it.
|
|
|
|
|
I thnk you forgot the L prefix.
Use the best guess
|
|
|
|
|
That isnt going to work.
As Richrd says it needs to be const wchar_t* string = L"string"; or at the vey least use the T() macro and use tchars.
==============================
Nothing to say.
|
|
|
|
|
Yes, I realise that now. 
I've been avoiding wide-char & unicode for as long as possible because it does my frickin' head in. Only now am I coming to regret not dealing with it sooner. 
"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan
That's what machines are for.
Got a problem?
Sleep on it.
|
|
|
|
|
Avoiding unicode? Why, its great! Really, all the languages, all the localisation taken care of, propper strings. No messing around! Go for it! 
==============================
Nothing to say.
|
|
|
|
|
The problem isn't unicode, the problem is (was) patchy support with certain windows APIs
having to switch between different encodings to get API-X to behave then switch back again. 
"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan
That's what machines are for.
Got a problem?
Sleep on it.
|
|
|
|
|
strcpy? Ever looked at that? Even beter strncpy, is that what you mean?
For example;
char mystr[100];
memset(mystr, 0, 100);
strcpy(mystr, "ask a better question");
==============================
Nothing to say.
|
|
|
|
|
Erudite_Eric wrote: char mystr[100];
memset(mystr, 0, 100);
strcpy(mystr, "ask a better question");
I have always held that less code is better code. When doing this kind of thing I prefer the syntax:
char mystr[100] = {0};
strcpy(mystr, "ask a better question");
which I think is clearer and lets the compiler do all the work.
[Also I would use strcpy_s() and probably several other stylistic issues...]
--
Harvey
|
|
|
|
|
Yeah, I actually allocate all arrays on the heap because buffer overruns are tracked better and dont trash the stack making it easier to debug so I always have the memset.
Of course dont forget the compiler is just doing the memset for you, it is invisible, but still takes place so isnt any different when the code actually runs.
==============================
Nothing to say.
|
|
|
|
|
Have a look at
char[]
Char[] are used to store ASCII string in C.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
