On 1 April 2016 at 09:53, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,
Nice to hear from you Igor. I am glad to see you around here.
Hi, Doru. Yeah, i am considering whether i want to return to things i left, or not. So, expect more of my acid sarcasm in future. Maybe :)
I do not see how your quote applies to the current case given that the original authors did not leave anywhere, but perhaps it was a joke, and I did not get it.
We all will leave sooner or later. The only what matters is what we left behind :)
Cheers, Doru
On Apr 1, 2016, at 5:54 AM, Igor Stasenko <siguctua@gmail.com> wrote:
A perfect example of careless programming. "I'll do it my way, and if it causing any problems, i don't care and i will just ignore them. And it's not my problem anyways, i went to something else already, since this part is works and DONE" :)
On 30 March 2016 at 14:33, Nicolai Hess <nicolaihess@gmail.com> wrote: Please don't do this:
updateHeight "no need to care about height, when it's logic is not customized" self layout isHeightCustom ifFalse: [ ^ self ]. [ self bounds: (self brickBounds withHeight: self customHeight) ] on: Exception do: [ "just skip and do nothing" ]
This makes debugging GLM/Brick ui/layout code with "self haltOnce" impossible. see GLMBrickGeometryTrait>>#updateHeight GLMBrickGeometryTrait>>#updateWidth
And if you log out the raised exception, you see some calls to not initialized fonts and a ZeroDevide and some more errors. The above catch, catches and hides wrong / to late initialized objects.
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com www.feenk.com
"No matter how many recipes we know, we still value a chef."
-- Best regards, Igor Stasenko.