C / C++ / MFC

Re: "Selecting all entries on Ctrl+A of key board"

6-Mar-07 1:13

sorry i didnt know it was posted after i tried cancelling it.. anyways do you have some answer to my ques?

harsha

Rajesh R Subramanian6-Mar-07 1:26

Rajesh R Subramanian

6-Mar-07 1:26

Look at MSDN for GetKeyState and GetAsyncKeyState. Use these functions with the virtual key codes of "Control key" and the 'A' key while you handle key down event in your application.

Absence is to love what wind is to fire; it extinguishes the small, it enkindles the great - Comte Debussy-Rabutin

debug mode VS execution mode

Ayman Mashal6-Mar-07 0:20

Ayman Mashal

6-Mar-07 0:20

Hi
i want to know in terms of memory allocation what is the diffrence between the debug and execution mode

i have a code that work fine in debug mode and finish successfuly while its faild in execution mode
with the error :
The instruction at "0x...etc" referenced memory at "0x000000002c" .The memory could not be "written"

my code is :

<br />
for(i=0;i<stringLength;i++)<br />
	{<br />
		<br />
		dSegment.segment=(int *)realloc(dSegment.segment,sizeof(int)*(++dSegment.DC));<br />
		dSegment.segment[dSegment.DC-1]=string[i];<br />
		printf("%d  %c\n",i,string[i]);<br />
	}

and the declaration of dSegment is

struct <br />
{<br />
	unsigned int DC;<br />
	int *segment;<br />
}dSegment;

thank in advance

James R. Twine6-Mar-07 1:06

James R. Twine

6-Mar-07 1:06

Ayman Mashal wrote:
0x0000002c

   That address tells you that you likely did something off of a NULL pointer, so I would start there.

   If the calculation of the memory size used in the call to realloc(...) is broken, and it looks possible because there is no testing/verification visible in the code you provided, realloc(...) can return a NULL value, and the following line would cause an exception in that case.

   BTW - the allocation differences between release and debug are many, and some objects (like MFC's CString) even allocate memory differently in release mode than in debug mode (it allocates exact amounts in debug, but allcoates in blocks in release). The first thing is that under debug mode, memory allocation routines will often pad allocated memory with special bytes allowing you to detect overruns.

   Are you sure that you have no memory-related issues in debug mode? You have to run the program to completion to find all of them, not just stop it in the debugger.

   Peace!

-=- James
Please rate this message - let me know if I helped or not!<HR>If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles

Ayman Mashal6-Mar-07 1:43

Ayman Mashal

6-Mar-07 1:43

you are right

at some point realloc returns NULL !!!! why ?
the calculation of the memory size is fine i put some print messages in the code and here is the output :
DC: 0
before realloc : 0
after realloc : 323b78
DC: 1
before realloc : 323b78
after realloc : 323b78
DC: 2
before realloc : 323b78
after realloc : 323b78
DC: 3
before realloc : 323b78
after realloc : 323b20
DC: 4
before realloc : 323b20
after realloc : 323b20
DC: 5
before realloc : 323b20
after realloc : 323b20
DC: 6
before realloc : 323b20
after realloc : 323b20
DC: 7
before realloc : 323b20
after realloc : 323b20
DC: 8
before realloc : 323b20
after realloc : 323b20
DC: 9
before realloc : 323b20
after realloc : 323b20
DC: 10
before realloc : 323b20
after realloc : 323b20
DC: 11
before realloc : 323b20
after realloc : 323b20
DC: 12
before realloc : 323b20
after realloc : 323b20
DC: 13
before realloc : 323b20
after realloc : 323b20
DC: 14
before realloc : 323b20
after realloc : 323b20
DC: 15
before realloc : 323b20
after realloc : 323bc0
DC: 16
before realloc : 323bc0
after realloc : 323bc0
DC: 17
before realloc : 323bc0
after realloc : 323bc0
DC: 18
before realloc : 323bc0
after realloc : 323bc0
DC: 19
before realloc : 323bc0
<big>after realloc : 0</big>

note that if i decrease my string length its work fine !!
is there any place in the project setting the sets the allowed space for the programme ?

thanks

David Crow6-Mar-07 2:57

David Crow

6-Mar-07 2:57

Ayman Mashal wrote:
at some point realloc returns NULL !!!! why ?

Gotta love realloc()!

"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15

"Judge not by the eye but by the heart." - Native American Proverb

i," Selecting All entries by on Ctrl +A"

toxcct6-Mar-07 10:14

toxcct

6-Mar-07 10:14

I reiterate :

"Surviving The Release"[^] by Joseph Newcomer

[VisualCalc][Binary Guide updated! ][CommDialogs new! ] | [Forums Guidelines]

harsh_29616-Mar-07 0:17

6-Mar-07 0:17

Hamid_RT6-Mar-07 0:36

6-Mar-07 0:36

Three same messages Sniff | :^)

WhiteSky

harsh_29616-Mar-07 1:08

6-Mar-07 1:08

ok it was by mistake.... you have some answer? Smile | :)

harsha

Hamid_RT6-Mar-07 7:12

6-Mar-07 7:12

What was question;)

WhiteSky

harsh_29616-Mar-07 18:46

6-Mar-07 18:46

ok question is.. i hav a list control in my dialog and i should have provision to select all the entries in it on Ctrl+A down like it happens in standard windows dialogs

harsha

Hamid_RT6-Mar-07 19:17

6-Mar-07 19:17

When you click on the listctrl(Ctrl+A) it selects all items what problem?

WhiteSky

harsh_29616-Mar-07 19:22

6-Mar-07 19:22

no its not selecting automatically like that.....

harsha

Hamid_RT7-Mar-07 6:53

Tabcontrol background color

7-Mar-07 6:53

Hi harsh,
When I wa clicking on my program (Ctrl+A) all items are selected,and then when I want to read them use of GetFirstSelectedItemPosition /GetNextSelectedItem
I dont have my code now,but use of this code SetItemState(Index, LVIS_SELECTED, LVIS_FOCUSED); and now what happens?And reply to me it work or no,please;)

WhiteSky

deeps_cute6-Mar-07 0:04

deeps_cute

6-Mar-07 0:04

how to change the background color for tab (to be same as screen)

Arise Awake Stop Not Till ur Goal is Reached.

Re: Tabcontrol background color

Hamid_RT6-Mar-07 0:11