Re: DPU-414 terminal

[Thomas S. <t.s...@fz...>]

> Can you work out where/why the loop happens?

well...
the loop is not endless, but stepping
from  4294967266, 135
to 350,  135
stepsize 1
takes a loooong time...

this '4294967266' was meant as '-30' in 'term.c' procedure 'test_term'.
it was produced by
(*t->move) (xmax_t / 2 - t->h_char * 10, ymax_t / 2 + t->v_char / 2);

xmax is 320  (because of 'dpu414 draft')
t->h_char is 19  (because of 'dpu414 large')
and 160-190 is -30, but it's interpreted as 'unsigned int' by 'b_move', so
it's 4294967266.

and then b_vector(350, 135) is called which then calls b_line(4294967266,
135, 350, 135)
which takes a long time to step from 4294967266, 135 to 350, 135

how to repair this?
check every call to 'b_move' and 'b_vector' (i.e. '*t->move' and
'*t->vector') that all arguments positive?
everywhere, where 'b_move' and 'b_vector' are called?
that's a lot of work...
but i don't see another solution

thomas
-- 
View this message in context: http://www.nabble.com/DPU-414-terminal-tp17371497p17403380.html
Sent from the Gnuplot - Dev mailing list archive at Nabble.com.