On Sept. 11, 2014, 10:19 p.m., Aleix Pol Gonzalez wrote:
Why is the component responsible for defining how it's going to be visually
integrated with the host application?
Do we get to hit the scrollbar if the component doesn't have a margin and
it's by the screen's border?
Hugo
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120147/
---
Review request for KDE Frameworks and Christoph Cullmann.
Bugs: 158379
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120147/#review66286
---
Ship it!
The patch looks good. Please commit. If we find
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120147/
---
(Updated Sept. 11, 2014, 9:24 p.m.)
Review request for KDE Frameworks
On Sept. 11, 2014, 7:39 p.m., Dominik Haumann wrote:
src/view/kateview.cpp, line 373
https://git.reviewboard.kde.org/r/120147/diff/1/?file=311597#file311597line373
this should be right spacer, right? :-)
All fixed. Will push. Thanks for the review. Don't hesitate to ping me in case
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120147/#review66298
---
Why is the component responsible for defining how it's going
On Sept. 11, 2014, 10:19 p.m., Aleix Pol Gonzalez wrote:
Why is the component responsible for defining how it's going to be visually
integrated with the host application?
Do we get to hit the scrollbar if the component doesn't have a margin and
it's by the screen's border?
Why is
