Search results for query: *

C allowed to make simple function pointers (ie without specifying the exact amount and type of parameters), but then you had to make sure you call it correctly through a pointer, so you dont mess the stack up. C++ does a better type-checking so you're not allowed to do the old way anymore...

Have you already created a class for the dialog? ------------------ When you do it, do it right.

in JScript you get aaa as a variable, not text, so change the line into the following: "ShowAlert('" + this.str +"'); " btw, use [ code ], [ /code ] tags when posting code. ------------------ When you do it, do it right.

cpjust - you just proved him wrong. And I asked him to prove himself right. short is 16bits.. at least on Microsoft platforms.. be it 16bit, 32bit or 64bit platforms or compilers. ------------------ When you do it, do it right.

First of all, can you imagen passing parameters to a DLL? I dont, because it's not an application, it's just a library (Dynamically Linked Library or smth like that). So, you either add an export function that you pass parameters through, or you add a public class method to do that...

xwb, can you prove this "If you use the 32-bit Microsoft compilers, a WORD and DWORD are the same size!!!" ? as far as I've checked, WORD is always unsigned short, which is 16bit, and never 32bit.. ------------------ When you do it, do it right.

That's just because in C# combobox lists objects, not strings. Kinda stupid looking for those coming from C++ to be honest. ------------------ When you do it, do it right.

The way I'd use it ((ValuePair) comboBox1.SelectedItem).KeyValue = newVal; ------------------ When you do it, do it right.

Properties such as WHAT? such as called by SOMEONE Ambient? how about sharing an example of what you need to understand? ------------------ When you do it, do it right.

if you define the aim of this, maybe we could be better at explaining you why you should go with standard length data types? ------------------ When you do it, do it right.

if I understand this correctly, you have Sample project files still refering to files named after older DirectX version. So all you have to do, is rename the library references in your Sample project file to new file names, provided with new DirectX version. ------------------ When you do it...

You either need to define the function as: _declspec(dllexport) void CreateFile().... .. or define the export entry in .DEF file to be able to access the function from outside. ------------------ When you do it, do it right.

Why not read line by line or block by block (saving memory that way) from the original file, and write only the needed lines or blocks into new file. Then delete original file, and rename the new file.. Seems a better decision to me, than a filepos jumping or reading a big chunk of file data...

ComboBoxes are not dumb.. and you dont need any hash tables to have more data on them. As you might have already noticed, ComboBox.Items.Add requires an object variable, NOT just a string. This means you can add actual objects to the list, whose structure is up to you. Just dont forget to set...

It much depends on what kind of projects you have. If you want to pass something between 2 processes (EXE application for example), you'll need to use on of those many interprocess communication methods (simplest being a file or registry entry). If you need to communicate between EXE and DLL...

Timer class is for timed jobs.. I dont see any timed jobs in this problem. Use System.Threading.Thread class to create "worker" threads that deal with each of the IP address. The logic would be to put the "working" part, i.e. the code inside the loop into thread function and let it run in...

To be honest, what is the problem of moving whole memory allocation to Initialize type of function? Use constructors just to set everything to default values, and perform allocation in a seperate function - you'll be off with current problems in no time. ------------------ When you do it, do it...

jmeckley, @ is used to ignore string escape character \. There's nothing it could help in the described situation. ------------------ When you do it, do it right.

Create a BITMAP object out from your pixel data, associate it with the DeviceContext and BitBlt it into your destination DC. ------------------ When you do it, do it right.

I do it like this: 1. Create the main form for all wizard steps. It contains the back, next, cancel buttons and if needed, a panel for controls. 2. Create a seperate custom control for each step of wizard. 3. By pressing Back, Next, just change the custom control in the panel...