| Age | Commit message (Collapse) | Author |
|---|
|
Starting with fltk-1.3.3, we can't use fl_oldfocus, this patch
fixes this problem.
IOW. this patch is necessary to link with fltk-1.3.3.
|
|
http://lists.dillo.org/pipermail/dillo-dev/2014-November/010273.html
A couple of months ago, Lauri Kasanen made some changes to fltk's linker
stuff, and I guess we're seeing the effect here.
As for focus behaviour being screwy, if you click on a page to give it
focus, then move the cursor away and then back onto the page, it won't
get focus again -- focus will go to an input or the location bar or
something.
|
|
|
|
|
|
(I had made it use that less-clear int[][2] interface because fltk2 let you add
all of the vertices in one call.)
It feels good to change that nasty-looking pointArray in Polygon::draw().
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The drawBorder{Top,Bottom,Left,Right} functions are similar. They
use a trapezium as draw polygon, or drawTypedLine() for dots and dashes.
Although the concept is simple, achieving pixel accuracy is laborious [1].
[1] http://www.dillo.org/css_compat/tests/border-style.html
|
|
|
|
To avoid artifacts we need clip with a rectangle that is line_width()
larger than our expose area.
Noticed by: corvid <corvid@lavabit.com>
|
|
Make currently exposed area available in FltkViewBase and use it to
clip rectangles to the required size before drawing them.
We can use the same mechanism to limit drawImage() calls instead of
doing it in dw/image.cc as currently done.
|
|
* allow negative width / height
* clip rectangle to size of the view. This avoids issues with 16 bit X11
coordinates overflowing and seems to improve performance.
|
|
We always need to set a clipping rectangle when drawing to
avoid that text "leaks" out as in the following
test case (by corvid):
<input type="image" name="name1" src="whatever"
WIDTH="80" HEIGHT="14"
alt="name1name1name1name1">
<input type="image" name="name2" src="whatever"
width="9" height="14"
alt="name2name2name2name2">
|
|
|
|
|
|
|
|
|
