Grrr...still I struggle with Outlook. I'm giving real thought to setting myself up with a new POP account and using a web client so that at least I can format emails the way I want.
Responses below... -----Original Message----- From: Keiron Liddle [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 29, 2003 5:10 AM To: [EMAIL PROTECTED] Subject: Re: source for hz algorithm >> The idea I am working with (of which I have prototype working) is that a break is after a line. For this break it finds the BPD distance from the top down (flow layout manager) from the start of the page to the current break. It also finds the keeps from the current break position, looking at parent layout managers and next layout managers for keep with previous. A best break is found based on these two values. A next break is then found, since we don't know we have a best until there is a worse break. This can be done for all pages in the page sequence or until forced break. >> This might be semantic nitpicking more than anything, but how can finding a worse break prove you have the best break? Wouldn't you have to find all possible breaks and verify that they're "worse"? Also, just for personal enlightenment, what principles govern "betterness" or "worseness"? >> Then if for example we want to find the optimum break. There is also the possiblity to get the next break within a context (which invalidates all further breaks) or previous break. << Could you please expound on this idea a little further? I don't think I'm quite following. >> The only drawback is that it constantly needs to find the child layout manager that applies to a given break and that finding the BPD distance could be time consuming in some circumstances. Optimisations should help a bit. << Offhand, I would think that this won't represent a reall performance bottleneck, and it would seem quite necessary given my somewhat green understanding of what you're proposing. >> I am hoping that making the breaks simple and easy to find certain properties from any position will help us to explore what to do next. << I'd really like to see this feature in motion. Being able to find this seems imperative for handing conflicting constraints and other anomalous situations. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
