|
Lists of words exists on the web, those are usually free ( words themselves ), but all the associated information are copyrighted to each dictionnary ( definitions, examples, linguistic info, ... ), and rarelly you will find multi-lingual lists.
normally, those are build manually word by word, and definition created by linguists and language experts.
Maximilien Lincourt
Your Head A Splode - Strong Bad
|
|
|
|
|
I want to develop a simple .dll, or application that deletes images from a usb digital camera. I don't have to use WIA, however I have been looking for tutorials or source code and I can't find any. MSDN has IWiaItem::DeleteItem, but I don't know how to use since it doesn't provide samples. The application/.dll has to be gui-less. ANY help would be greatly appreciated.
Mike - I love to program!
|
|
|
|
|
Hello all,
I have a question about doing an increment of a Void* pointer. I find out that I cannot do something like this
<br />
int i[10];<br />
void* p = i;<br />
int j = *((int*)(p++));<br />
The compiler will complain about the size of the pointer when I try to do an increment. My alternative approach is
<br />
int i[10];<br />
void* p = i;<br />
int j = *((int*)(((char*)(p))++));
First, I type cast the void* to char*, and then the compiler will know when I do the increment, it is going to add 4 bytes each time. I think this approach is ugly and might not compatiable with different platforms (when char* is not 4 bytes).
In case if people wonder why I try to do something like this is that I try to calculate the offset in an array by my self with only know the size of the element in the array in the array. However, I don't know how to add exactly n byte to a pointer when calculate the offset. The default increment behavior always requires to know the type of the pointer, which I don't know. Any idea?
Thanks!
Nacho
|
|
|
|
|
Rather than using a void*, I suggest using a BYTE*. you can then add whatever size you need without worrying about casting. You then simply increment the pointer by doing operations comparable to: p += sizeof(int);
Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke
|
|
|
|
|
Thanks, but is there any way which just use ANSI C++ standard type rather than BYTE? By using BYTE, we will have problem when we port the code in other platforms. Any idea?
Nacho
|
|
|
|
|
Use unsigned char. (Or use BYTE and on platforms that do not have it defined or typedefed, typedef it yourself.)
Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke
|
|
|
|
|
arey yar
that above one Immpossible.
v.raju
|
|
|
|
|
Why are you using a void pointer? If you want to point to an int why not use an int*? Since void* can point to anything the compiler has no way of knowing the size of the object pointed to. In your code when you done p++ how far did you expect the pointer to be advanced?
Steve
|
|
|
|
|
The arithmetic for void* is not defined, so if you need pointer arithmetic you must do it with a type other than void*. However, the void* is guaranteed to be capable of holding any address on the machine, while other types of pointers do not guarantee it. But, for practical purposes on practical platforms with practical processors you may consider that all pointers are interchangeable.
This means that your code should be re-written to:
int i[10];
void* p = i;
int j = * (((int*)p)+1);
In other words: first cast the void* to int*. On practical systems this conversion does not produce any machine instructions, so it is not really executable code. This means that performance is not an issue.
After the cast the compiler treats the pointer as an int*, so the "+1" arithmetic is well defined (equivalent to "++"). It will be, in fact, equivalent to advancing the pointer to the address where the next int lies. In Win32 this will be an increment of 4 bytes. I've seen SOLARIS implementations where this same code would produce an increment of 8 bytes, to correctly handle its 8 byte int's.
The code I wrote is perfectly legal ANSI, compiles and runs correctly on all platforms, and I wouldn't consider it ugly. Your original code too, except that the precedence is not correct (you increment while the pointer is still void* and at that point it has no arithmetic logic).
Anyway, the second piece of code you propose should not compile. But that can be easilly fixed with "+1" instead of "++". But your reasoning changed in the second example, since you forced the cast from void* (that has no arithmetic logic) to char* (that has arithmetic logic) before incrementing, and so the increment is well defined. However, the increment amount is not correct, because sizeof(char) is 1 and not 4. The char*++ points to the next character (1 byte), instead of the next int (4 bytes). That should have resulted in a bad value for j. Didn't it?
Anyway, below is a piece of code you can test. I initialized "i" to show you that "j" gets a bad value (after fixing from "++" to "+1"). Also, you can see that "k" and "m" get the correct value. As a final note, the code for all 3 integers "j", "k", and "m" as the same instruction type and count, and their efficiency is the same. Of course "j" is wrong, but the compiler doesn't know that (however, some processors may generate exceptions when integers are not aligned, which may result in crashes or slow operating system exception handling).
The "ip" and "n" are not as efficient as the cast versions of "j", "k", and "m" in the debug version. In the release version they should be much more efficient, but the use of the "ip" is most adequate to situations where performance is not an issue, or you intend to do multiple accesses and manipulate the address of the pointer often, or you want the code to be clear. The manipulation could also be done with incrementing indexes in the "m" example, of course.
#include <stdio.h>
void main(void) {
int i[10]={ 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009, 1010 };
void* p = i;
int j = *((int*) (((char*)(p))+1) ); // Ugly
int k = *(((int*)p)+1); // Pretty
int m = ((int*)p)[1]; // Also pretty
int* ip=(int*)p;
int n = *++ip; // Even prettier
printf("j=%d, k=%d, m=%d, n=%d\n", j, k, m, n);
}
Rilhas
|
|
|
|
|
hi,
how will you display an icon on a button(CButton MFC VS2005 ), the icon is in say a fil c:\something.ico
|
|
|
|
|
First u have to load the icon using LoadImage() function.. then u will get a handle(HICON) for the icon. Now Pass this handle in the SetIcon function of the CButton
nave
|
|
|
|
|
HICON hicon=(HICON)LoadImage(
AfxGetApp()->m_hInstance, MAKEINTRESOURCE(IDR_AnswerTYPE),IMAGE_ICON, 48, 48, LR_DEFAULTSIZE);
m_Button1.SetIcon(hicon);
and you need to set icon in property window from your button to true.
|
|
|
|
|
thankx a lot guys. Problem solved.
Appreciate the help
|
|
|
|
|
 how comparing similar images to determine how they differ and by how much.? any idea?any code please?
|
|
|
|
|
This is infact not a simple question. I can provide you with hint that try to make Gaussian modal of both images and then compare them. So try to study Gaussian modal first. I hope it helps.
Good luck
We Believe in Excellence
www.aqueelmirza.cjb.net
|
|
|
|
|
The only reliable general purpose image comparison techniques currently available work at a low level. For example, imagine image 1 is a picture of you, and image 2 is a picture of you holding a red ball.
Current gneral purpose comparison techniques don't try to understand that both images contain the same person, and that they are diferent because there is a ball in the second one. Intead, the most reliable techniques today start by subtracting both images and detecting which portions result in a non-zero value. These techniques are the basis for video compression today.
So, your question is not specific enough. What diferences do you which to detect? If you are trying to determine what is diferent in the "meaning" of the pictures then good luck! It is an active area for research, and there is no general solution for it on the horizon. For specific solutions (like detecting that in one image the person has the eyes open and in the next the eyes are closed, or that a room is empty in one picture and not empty in the next) solutions already exist in various domains.
If you intend to determine changes at a lower level then several techniques exist. But be prepared for a very computationally intensive topic, so get yourself a fast processor and be prepared to use C/C++ or even some assembly language!
Rilhas
|
|
|
|
|
im looking for a place where i can find a list/guide of the microsoft standards for a GUI eg how many DU's between radio button etc
thanks
|
|
|
|
|
|
I have a program which has a total of array size of 94000 float(31 arrays).
When I change 9 of the arrays (73737 size) into double, my program seems not working.
Is the total array size too big ?
How to fix the problem ?
Thanks for any help.
|
|
|
|
|
Typically, when you need an array of more than a few hundred elements, it is best to allocate the array on the heap. This allows you to create arrays bounded only by memory (or 2GB if on w32).
onwards and upwards...
|
|
|
|
|
Thanks for the advice.
You mean I should using pointers ? I am a programer from Fortran/Java. I have not got used to pointers. Give me detailed or further advice please.
|
|
|
|
|
For the array, in order to use the heap memory, you can allocate your array like this
<br />
float* floatArray = NULL;<br />
floatArray = new float[100];<br />
and when you finish using your array, you can
<br />
delete [] floatArray;<br />
floatArray = NULL;<br />
I wish it help!
Nacho
|
|
|
|
|
Thanks Nacho. I have implemented your code suggestion.
|
|
|
|
|
Thanks for the advice.
You mean I should using pointers ? I am a programer from Fortran/Java. I have not got used to pointers. Give me detailed or further advice please.
I particularly use six big arrays a[8200],b[8200],c[8200]
Ideally I need to expand my program to a[16400],b[16400],c[16400]. However, I tried these expansion, the program stopped to work. message says: memery problem.
-- modified at 15:27 Monday 24th April, 2006
|
|
|
|
|
using pointers will not fix all your problems but will help you deal with memory problems.
normally, when allocating memory on the heap ( with new ) you will have a immediate result telling you that the allocation worked or not.
Maximilien Lincourt
Your Head A Splode - Strong Bad
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
