Re: vt_core.c vt_is_cursor_in_area different behavior after r282823

2015-05-13 Thread Ed Maste
On 13 May 2015 at 03:02, Marko Turk mark...@markoturk.info wrote:
 Hi,

 after r282823, new vt_is_cursor_in_area is, in some cases, returning
 different values than the old function.

 For example:
 If (my + vd-vd_mcursor-height) is equal to (area-tr_begin.tp_row),
 old function will return 1 and new function will return 0.

 Is this intended behavior or is it a bug?

Thanks for the detailed look at the change! It's intentional -- when
they're equal the cursor rectangle and display area rectangle border
each other, but do not actually overlap. It doesn't hurt to return 1
in this case, it just results in some unnecessary drawing.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


vt_core.c vt_is_cursor_in_area different behavior after r282823

2015-05-13 Thread Marko Turk
Hi,

after r282823, new vt_is_cursor_in_area is, in some cases, returning
different values than the old function.

For example:
If (my + vd-vd_mcursor-height) is equal to (area-tr_begin.tp_row),
old function will return 1 and new function will return 0.

Is this intended behavior or is it a bug?

BR,
Marko


pgpiROKPHB27F.pgp
Description: PGP signature