I ran into this as well. I tried to avoid triggering the deprecation, to see if the model understood initialExtent before sending it and guarding for nil models and things like that. otherwise just dispatching to the default extent, however this is difficult because all objects understand initialExtent! i needed a method respondsToButNotInObject:... at that point I got distracted. it is ugly to do this deep respondsTo: check so I was not sure what the correct way of approaching this deprecation was. I assumed someone had a nice solution when they deprecated it? Mike On Thu, Mar 4, 2010 at 5:49 PM, Alexandre Bergel <alexandre@bergel.eu> wrote:
Hi!
I do not have a solution, but Object>>initialExtent was recently deprecated and this causes great usability problem. This deprecation is very valuable for a clean UI separation. However, I have a warning deprecation each time a window is open. The reason stems from the method:
SystemWindow>>initialExtent     ^ model initialExtent
For now, in my image, I suppressed this deprecation. Again, I do not have a clean solution.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel  http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project