C / C++ / MFC

Correct pretty sure same thing is going to happen with your code, I wouldn't hold the dialog on the stack on a modeless dialog. It's pretty dangerous to do, hold it as local data in the first dialog or on the heap same as you would on a multitask code :-) In vino veritas

Yes standard console output is always buffered. You can actually easily remove it setvbuf(stdout, NULL, _IONBF, 0); setvbuf(stderr, NULL, _IONBF, 0); The problem is it will slow the console program down like a dog as each character invokes a full call. I sometimes do it when I have a embedded target with UART debugger like on the Raspberry Pi. In vino veritas

Fedrer wrote: Do I need to register tlb file like a com dll? You cannot register a TLB file. However you have to register the COM component (that is the DLL).

You are making hard work of it, you have a C11 compiler :-) Unionize the struct pointers .. they are all pointers to different types typedef union { void* void_ptr; struct mySmallStruct1_s* SmallStruct1_ptr; struct mySmallStruct2_s* SmallStruct2_ptr; struct mySmallStruct3_s* SmallStruct3_ptr; } smallstruct_ptr; struct mySmallStruct1_s { smallstruct_ptr ptrToNextElement; int myArray[1]; }; struct mySmallStruct2_s { smallstruct_ptr ptrToNextElement; int myArray[2]; }; struct mySmallStruct3_s { smallstruct_ptr ptrToNextElement; int myArray[3]; }; struct myBigStruct_s { struct mySmallStruct1_s mySmallStruct1; struct mySmallStruct2_s mySmallStruct2; struct mySmallStruct3_s mySmallStruct3; }; struct myBigStruct_s myBigStruct = { { .ptrToNextElement.SmallStruct2_ptr = &myBigStruct.mySmallStruct2, .myArray[0] = 0 }, { .ptrToNextElement.SmallStruct3_ptr = &myBigStruct.mySmallStruct3, .myArray[0] = 0, .myArray[1] = 0 }, { .ptrToNextElement.void_ptr = 0,.myArray[0] = 0,.myArray[1] = 0, .myArray[2] = 0 } }; struct myBigStruct_s myBigStruct1 = { { .ptrToNextElement.SmallStruct2_ptr = &myBigStruct1.mySmallStruct2,.myArray[0] = 1 }, { .ptrToNextElement.SmallStruct3_ptr = &myBigStruct1.mySmallStruct3,.myArray[0] = 1,.myArray[1] = 2 }, { .ptrToNextElement.void_ptr = 0, .myArray[0] = 1,.myArray[1] = 2,.myArray[2] = 3 } }; In vino veritas

methods are a C++ feature you can only mimic in C, suing function pointers and the like. For instance #include struct point { int x,y; void (*pfun)(struct point *pp); }; void getdis(struct point *pp) { printf("%d\n", (pp->x + pp->y)); } int main() { struct point p; p.x = 5; p.y = 10; p.pfun = getdis; p.pfun(&p); getchar(); return 0; }

luplup wrote: So please can you show me the right way to cast correctly That would require a book. You do it by understanding the data types that the pointer points to. What they represent, how they are represented in memory and what memory means in C (and computers in general) especially in relationship to the heap and the stack. And being very careful. If you wish to learn in detail then write your own printf() function and test completely.

I understand finally sorry I’m slow thanks so much

And what does your code have to do with the C / C++ / MFC Forum?

Dear Friend. The code works. But the output comes as stair steps. But, this is because of this sharpening .. and I want to alter . if you can give idea how to make the smoothing. v2 is the velocity of second layer. and v1 is velocity of first layer. maximum iterations is 10 with the percentage of threshold .. problem is that it gives sharp stair stepping. while I want to make like smooth signal in output. If you can guide.