|
can any one help...how to add separator line in list box just like menu items separator.
|
|
|
|
|
How about:
InsertString(x, "--------------");
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
If david's answer is good so AddString is good for you.
|
|
|
|
|
I thought it's already seperated
OK,. what country just started work for the day ? The ASP.NET forum is flooded with retarded questions. -Christian Graus
Best wishes to Rexx[^]
|
|
|
|
|
i can add string using m_listBox.AddString("------");
but now user is able to select ----- option.
what i want is:
i have list of items to display in list box, i want a separator in between some,and
user is not allowed to select separator line.( ----- ).
|
|
|
|
|
How do I convert INT32 to int?
For instance, INT32 nID = 10;
Thanks!
|
|
|
|
|
from MSDN.
INT32 32-bit signed integer.
This type is declared in BaseTsd.h as follows:
typedef signed int INT32;
Hence you don't even need the conversion.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
|
|
|
|
|
From MSDN only,
The size of a signed or unsigned int item is the standard size of an integer on a particular machine. For example, in 16-bit operating systems, the int type is usually 16 bits, or 2 bytes. In 32-bit operating systems, the int type is usually 32 bits, or 4 bytes.
for 64-bit OS, ..., he didn't specify which machine he is using
|
|
|
|
|
Provided he is using MS C++ compiler a int is a 32 bit type, see http://msdn2.microsoft.com/en-us/library/cc953fe1.aspx[^].
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
|
|
|
|
|
quote from your link
Type int is an integral type that is larger than or equal to the size of type short int, and shorter than or equal to the size of type long.
link to size of int http://msdn2.microsoft.com/en-us/library/ed98zksd.aspx[^]
CPallini wrote: using MS C++ compiler
not mentioned
|
|
|
|
|
Rajkumar R wrote: using MS C++ compiler
not mentioned
Have you seen forum title, haven't you?
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
|
|
|
|
|
Have n't u seen the links i provide (size of int )
|
|
|
|
|
Yes but if he needs to convert a INT32 that is, by definition (unless he isn't using the BaseTsd.h header), a signed int then the assignment
INT32 i32 = 10;
int i = i32;
it is valid.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
|
|
|
|
|
when int is 16bit it truncates . ok just started as joke
modified on Monday, February 11, 2008 11:27 AM
|
|
|
|
|
On a 32 bit machine, int is just 32. On a 64 bit machine, int becomes 64 but INT32 would still be 32. Or I'm wrong ?
OK,. what country just started work for the day ? The ASP.NET forum is flooded with retarded questions. -Christian Graus
Best wishes to Rexx[^]
|
|
|
|
|
I was thinking that the size of int depended on the machine, too, but on the website mentioned above by CPallini, it says that the size of int (and unsigned int) is 4 bytes, and that __intn (where n is 32, 64, etc) specifies that a specific number of bytes is used. So it sounds like maybe int is always the same as INT32?
Now I'm confused about whether INT is the same as int or __intn. That is, do the capitalized versions of data types (INT, UINT, LONG, DOUBLE, etc.) depend on the machine, unless specified as INT32, INT64, etc?
Thanks!
|
|
|
|
|
The size depends on how the compiler interprets the data type, which is
usually based on the target machine type.
For Microsoft specifically, int, long, INT, LONG all remain 32 bits regardless
of compiling for 32 or 64 bit.
Remember, the capitalized versions are Windows types, not C++ language
types.
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Microsoft wisely chose to keep the int and long data types 32 bits wide,
even in the 64-bit compiler.
This is microsoft-specific - other compilers may have different widths for int and long.
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Thanks! That's very helpful.
One last question: if you wanted to use type int and be sure its size was 4 bytes regardless of what compiler was used, is there any standard way of doing this?
|
|
|
|
|
From the docs:
"The types __int8, __int16, and __int32 are synonyms for the ANSI types that
have the same size, and are useful for writing portable code that behaves
identically across multiple platforms. The __int8 data type is synonymous
with type char, __int16 is synonymous with type short, and __int32 is synonymous
with type int. The __int64 type has no ANSI equivalent."
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
But the documentation says that __int8, __int16, __int32 and __int64 are Microsoft-specific. Isn't that the same as saying you must be using the Microsoft compiler to use these types? I was looking for something that would also use the same number of bytes if the Borland compiler or some other compiler was used.
Thanks.
|
|
|
|
|
They're actual keywords in Microsoft, so in that sense they are MS specific.
They can easily be defined (using macros or typedef) on other compilers if
necessary.
Until there's some standard for this, all compilers will need to define the size-specific
int types somehow
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Thanks for the good information. A big 5 gold star for you!
|
|
|
|
|
Heh no problem - and thanks for the gold star!
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Thanks Mark
OK,. what country just started work for the day ? The ASP.NET forum is flooded with retarded questions. -Christian Graus
Best wishes to Rexx[^]
|
|
|
|