Dmitry Suzdalev
Dmitry Suzdalev
I am currently trying to achieve the same and I plan to do it like this: Let's say my view is split into 2 parts: **M**ain and **A**nchoredToBottom. If there...
Oops, this won't work because there's no way to know `bottom()` of whole contour layout in `contourHeightOf { }`...
Another feature I constantly wish to have is having `maxOf()`, `minOf()` being available not only for 2 parameters, but any number of them (varargs?). This can be worked around with...
I now feel I shouldn't have mixed min/max in this issue. I actually was referring not to `minOf/maxOf` on solvers, but rather their overloads on `XInt/YInt`. I sometimes find myself...
Yeah, I did extension function for `minOf(XInt/YInt)`, like this: ```kotlin fun ContourLayout.minOf(y1: YInt, y2: YInt, y3: YInt): YInt { return minOf(minOf(y1, y2), y3) } ``` but unfortunately I can't do...
I have 9 crashes in my Firebase console with exactly this stack trace. Judging from analytics events which in my case get attached to the crashes, this happens when user...
Mosby Conductor version is `3.0.0`, Conductor version is `2.1.4`
I see, thanks, will folow that issue too.
I think that attaching and detaching view in presenter should follow the actual lifecycle of a view in the Conductor library. For example in my mvp-based app I rely on...
Ah, I see. Those modules, sometimes they seem to multiply at an unusually fast rate! :) This issue should be closed then I guess...