All the code an individual project needs to build must be part of the project, or available to the project through a library. How you manage the physical files is up to you. I personally use a "common" folder in the solution's folder to keep my common/shared cpp/.h files in one location - only one codebase to update. All projects can reference files there using relative paths, something like "..\common\somecommoncode.h". Mark Mark Salsbery Microsoft MVP - Visual C++ :java:

Hi, Whilst not necessarily the perfect solution, you could inline the operators. class B : public A { ... public: inline A& operator << (double & atr) { return A::operator << (atr); } }; This might be a useful workaround for your scenario. Lea Hayes

Budric B. wrote: It doesn't have that much behavior other than a constructor and a destructor to free the memory. The reason I was doing it this way was because I would be adding more data members to describe the data later. But you're probably right that it wouldn't add that much performance loss to write each data member. I'll have to time it and see. Watch out for the copy constructor and assignment operator, since the compiler will generate invalid forms and call them freely. Budric B. wrote: I've made a workaround where I allocate 2 buffers, 1 for the object and one for the data, the rest of the code stays the same. That doesn't trigger the assertion. However I don't know if the object's memory gets freed or not since I'm still calling delete Voxels and not delete [] voxels; I think that should work. The main difference between delete and delete[] is the way destructors are called, which shouldn't be a problem if it's just data. Nathan

thanks for the heads up on the flag, I'll try it with my code.

I spent way too much time on this problem, that's why I know ;)

There should be an API to detect if there are open handles on a particular file. At least, there is a utility called 'Task Manager Extension' in CodeProject which is able to enumerate through the open handles on a file. Check out http://www.codeproject.com/system/Task_Manager_Extension.asp[^] Vasudevan Deepak Kumar Personal Homepage Tech Gossips

Jim Crafton wrote: ...if you're using WaitForSingleObject() to do the "waiting" and not a busy wait while loop. Correct. WaitForSingleObject() uses no CPU time while waiting for the object state to become signaled or the time-out interval to elapse. "Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

Also I have a class that I derrived from CDialogBar. Inside it I have a function to disable my controls that contains something like: CWnd *test = this->GetDlgItem(IDC_ADDKEYFRAME); test->EnableWindow(FALSE); this doesn't disable the button. Why not? I've also tried adding control variables and initialize them using DDX. The variables get initialized, the HWND value match what I get from GetDlgItem call, but the button never gets disabled.

So, what is the difference between ** and [x][y]? Well, one is a static memory location and the other are pointers. float **x; float y[10][3]; x is a pointer to a pointer. So, what the compiler does it it goes to the address of the variable X. It then reads this address and then goes to the address stored at that location. It then uses this address as the place to store the float! If you understand single pointers you can see how the double pointer works: First Address = *x; Second Address = *First Address; The Actual Float Value = *Second Address; At any level you can actually allocate a "block" of pointers that you can index into at that time. So what's the difference with an array? y\[1\]\[2\] = 12; Is actually y\[3 + 2\] = 12; It's a single block of memory! There are no pointers! In the case of even a single float *, the address of the variable stores the address that then stores the actual value! In the case of an array, the address of the variable stores the actual value! So, a multi-dimentional pointer is actually a single block of memory that is then index by the compiler as one block. So if you have: rows by columns: float x[row][column] each row is maxcolumns size. So if you want to go to rowx, coly, you could simply do rowx*maxcolumns + coly. This would index that block of memory. The compiler knows how to generate the correct code if it's an array or pointer. Remember, an array's address stores the actual data. The pointer's address, stores another address. That address then stores the data (in a single indirection case). 8bc7c0ec02c0e404c0cc0680f7018827ebee

http://www.codeproject.com/miscctrl/#Beginners[^] "You're obviously a superstar." - Christian Graus about me - 12 Feb '03 "Obviously ???  You're definitely a superstar!!!" - mYkel - 21 Jun '04 "There's not enough blatant self-congratulatory backslapping in the world today..." - HumblePie - 21 Jun '05 Within you lies the power for good - Use it!

My GetPixel() function is the same as the code I posted. It just dereferences the pointer. On top of that it checks if the indices are within limits and if not it returns a 0. I rewrote my gaussian blur algorithm to use the memory directly, without GetPixel() and now my results are 10 times faster. BTW. Thanks for the @clk tip.

Thanks for your replies. I didn't want the thread to lock up so this is perfect, but I wanted to confirm that that's how it worked and I'm not missing some small part of code.

Thanks.

I guess people aren't kidding when they say don't modify the GUI from a thread. Don't modify the MFC GUI from a thread that did not create the MFC object - you can modify any of them from the same thread that created them, of course.

Well then that's the problem. MFC stores handles in Thread Local Storage, so they aren't available from another thread. It's not a good idea to update the UI from another thread anyway (http://www.codeproject.com/csharp/begininvoke.asp[^]. I'd suggest posting a message to the UI instead (using PostMessage) and handling the message there. Regards Senthil _____________________________ My Blog | My Articles | WinMacro

I don't see what the problem is - you're somehow assuming that every person who has written anything online about a gaussian blur is using the same maths formula that you are. That's the bit I'm trying to get through to you - if there are pages that show blurs which are almost the same as the ones you have, but don't quite fit the formula, then it's more likely that they are 'wrong', although the end result is indistinguishable from the results you are getting. Christian Graus - Microsoft MVP - C++

Christian Graus wrote: you use the fractional part to work out what percentage of surrounding, actual, pixels to use to determine a colour for the pixel that doesn't really exist that actually applies to nearly all interpolation methods. :) bi-lin just means using linear interpolation in two dimensions. (i know you know this - just filling-in) Cleek | Image Toolkits | Thumbnail maker