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?
(comments are locked)
|
|
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. Thanks for your answer. It helped me to solve the problem. A yield after a BeginArea was blocking the EndArea so it was opening a lot of areas.
Mar 01 '10 at 08:48 AM
eurosat7
My pleasure, glad it helped.
Mar 01 '10 at 11:14 AM
Ricardo
Thankyou for this it helped alot. was getting an in finite loop because i forgot GUI.EndGroup(); lol
Apr 06 at 08:05 AM
Packetstorm
(comments are locked)
|
