On Apr 8, 1:46 pm, Anton Zorin <zorinan...@googlemail.com> wrote:

Yes, essentially.  mouse-drag-selection (the highlighting of box
regions on the bitmap) does not need to be echoed in the *.box file,
while you select  (although, I guess, that would be a plus: to select
in either GUI (bitmap) or box file window, using any method (mouse,
keyboard, or both), and to have the other window automatically be
updated with the selection state), but everything just needs to be
updated everywhere in the end, somehow.

Tearing the *.box file apart is already easily done using popular,
text-friendly scripting (perl, python, ruby, etc.)

I didn't mean to suggest that the functionality would necessarily
belong in the same application as the one you are announcing in this
thread -- it's quite the reverse of your app.  But then, again, I can
think of situations where BOTH utilities would be useful to someone,
in one single project, and then it would make sense for them to be
part of the same utility suite

I was just hoping you might find it relatively easy to build the one I
describe only because you seem to know the GUI tool set -- and my
utility needs mouse-drag-select and gui stuff like that.  (And also
because it was sort of the exact reverse of mine :-)), in terms of
input/output data types)

a number of box editors out there do without a spreadsheet  per se.

That sounds optimistic :-))

thank YOU.