omega said:
Ah, ok, now I see. I've not after all an abort config for my clicking
accidently on unassociatated huge files. At least I could perhaps use
that edit setting for purposes of preventing my animals from tapping
text into eg one of my binary .gho images. Other than a scenario like
that (which is in fact real chez moi, precautions for the beasts doing
things to my files)? What would be a reason to set the edit max-size at
some particular reduced setting?
not clearly... you can open file, that is lagrer than this size limit,
and yes, can not edit it, unless you delete characters (so any animal
of yours can open your file, delete some important sentence from it,
save it back and exit (using simple esc key
and you will never know,
where the sentence, you thought that ought to be there, had gone...
well, what the size is for? i do not really know... microsoft's bunk..
as stated in sdk, every editbox must have a max-text-limit and no
'infinite' value is supported... so i wondered, is it better to use
quietly 0xFFFFFFFF as infinite and live with quilty conscience of
such a swindle, or let the user set his own max-value?
....jsimlo
p.s. i am a programmer and this is my way of thinking...
don't hide!
p.s.s. what kind of animals did you mean?
