On Wed, Apr 6, 2011 at 11:09 PM, Igor Stasenko <[email protected]> wrote: > Me neither. > I found it odd that some pieces of code relying that origin <= corner > (sorry i mistaken in previous mail) > > i meant that > > origin x <= corner x > origin y <= corner y > > and yes, there is some code that assumes it is always like that. > > So, yes. While in pure geometry two different corner points could > define a rectangle, no matter > in what order you put them, in pharo/squeak geometry it sometimes matters :) > > But of course you can try and figure out what is works and what not, > and fix it :)
hmm.. I am not sure if this would improve situation or make situation even more ugly, but maybe #origin:corner: could figure out how to create rectangle from given parameters that satisfies: new_origin x <= new_corner x new_origin y <= new_corner y in other words, resulting rectangle may have different origin and corner than one supplied to #origin:corner: Davorin Rusevljan http://www.cloud208.com/
