I think it's pointing to this code: (it is slighty modified - the real code is far more complex ;) )
I use p.SetBusy() and p.IsBusy() to avoid multiple requests for one image.
I use p.GetImageTexture() and p.SetImageTexture() for caching request responses.
So If I use caching and avoid asyncronous problems - why do I get something like a stackoverflow on the request buffer?
Don't use yield in OnGUI() between GUILayout.BeginArea() and GUILayout.EndArea()
answered Mar 01 '10 at 08:46 AM
Regarding GUIClips: The case where I remember getting that error was when I had a GUILayout.BeginArea that didn't have a corresponding EndArea (or in general, a GUILayout.Begin[Something] that didn't have the corresponding End[Something] call). Have you checked that is not the case elsewhere in your code?
What do you mean by "something like a stackoverflow"? What does p.GetImage() do ?
Also, notice that if what you want to do is to have the image change every time you press the button, the code will likely not work anyway, as you only obtain a new image if the imageTexture is null, which it won't be after the first time you assign it.
answered Feb 26 '10 at 02:32 PM