Type: Posts; User: OReubens
Search took 0.17 seconds.
the principle of RAII is that your destructors get called, so yes "it will handle it perfectly".
but there a couple special cases like the circular reference you mentioned where some "smart...
alternatively, depending on needs, you might be able to pick up a 2nd edition "really cheap" as some stores will be dumping their 2nd edition copies.
ok, so I'm going to assume what you want is curved surfaces in general...
If yes, then you have
nonuniform nonrational B-splines
nonuniform rational B-splines...
but "why" ?
you should view an imagelist as a collection of individual images. The fact that 'under the hood' this is implemented as a larger bitmap (actually a DDB) is...
Are you sure about that ? There's a difference between passing NULL as DC and passing the return value of GetDC(NULL) as DC. (or the return from CreateCompatibleDC(NULL))
it isn't documented on...
And that is my precise point...
you may leak resources other than memory, because the OS does not clean up EVERYTHING when your exe terminates. delete does more than just clean up memory, it...
if you use a 256 color image
then each pixel is a single byte, each of which is an index into the colortable
the color table is EITHER 256x 16bit combined RGB values, or 256xRGBQuads depending on...
Correct, but a somewhat incorrect view of things (which granted, is sometimes hard to get people to wrap their heads around).
Compilers are getting better, CPU's are getting better. This means...
you're looking for 3d splines ?
If yes, you'll need more info than that, you'll need an escape/normal vector on the point as well. ANd probbaly you'll want a 'force' value as well.
or do you...
looks like you have a somewhat awkward design. But without seeing the whole class, it's possible this is how it has to be.
CObject just being as it is, not as a template...
probably not needed, potentially this is going to slow down your app rather than speed it up.
if as functions, you're forcing calls, and restricting the compiler to manage registers on it's own...
1) It's bad advice to suggest delete isn't needed. especially to novice users which might take that as a carte blanche to apply it liberally.
2) as I said, yes, windows will clean up the memory....
unclear what you're asking, but if you create a 32x32 imagelist, then all images will be 32x32. Imagelist does not accomodate for images in varying sizes. You can 'sort of' accomodate by oversizing...
you cannot pass information from non elevated programs to elevated programs via IDropTarget (or via several other IPC methodologies for that matter), because that violates the UAC contract. For the...
no. you need to specify the palette the IMAGE is supposed to use. This is what you do by specifying the colors in the image's color table. (you only need to do this for 16 and 256 color bitmaps). ...
no, it fails because you pass NULL, Period. You can't create a dib section without a DC.
You should also correctly fill in biSizeImage. (in this particular case it would be width*height)
Depends what "navy" you refer to. If you refer to the american, then they're like most of the other US armed forces (and military in other nato countries for that matter) and are increasingly...
simple rules to follow
1) if you only want to pass a POD value or variable that won't allow the function to modify the variable that was passed in:
POD type: pass by value
anything else: pass by...
if you allocate with new
you should delete with delete
also, you don't have to set a pointer to NULL after a delete, unless you'll be testing/reusing the pointer.
No that tells Windows...
In this case, yes... to a degree, with some small issues if you can live with them :-)
you'll find that a regular button with a BITMAP on it will behave a bit strangely towards painting
July 30th, 2014, 12:13 PM
I meant to say that how the compiler solves the 'virtual' issue is entirely proprietary to the compiler. Many compilers solve it with a vtable, but that isn't the only approach.
July 30th, 2014, 08:09 AM
precisely BECAUSE a compiler can do microoptimizing a lot better than most programmers out there.
And giving a compiler "the raw code" will allow the compiler more leeway in optimizing than already...
July 30th, 2014, 07:45 AM
the first function defines a function that tabes a QSharedPointer object
the 'data' here is a COPY of the one that was passed in.
the 2nd takes a function that takes a QSharedPointer reference...
July 30th, 2014, 07:41 AM
"memory dumping" like you're doing here is not part of the c++ standard,
so the results will be dependant on the compiler used (even version could matter) and which settings you used.
Click Here to Expand Forum to Full Width
This is a CodeGuru survey question.