Hi Martin,
Ah, thanks for the comments. I've been meaning to talk to you about it,
but I still trying to work out exactly how I want to do this. (I'm very
new to this side of Abi.)
The first method, getAllAttrProp(), is fairly trivial. For ages I've
wanted to be able to see during run-time exactly what the current set
of properties is, without having to spam UT_DEBUGMSG. To this end I've
added a little table to the CocoaAbi palette which displays them
continuously, getting them via the above method.
I'm not sure what to do about selections, though; I would like some way
to merge two property sets with a result of all properties specified
and whether they have mixed or same values...
The others... well, I really don't know the best way to go about this.
I dislike specifying properties at inline/block level which match the
current default from the document style. For example, if using Normal
with black, non-italic, non-bold text, then there is a difference
between specifying "color: #000000; font-style: normal; font-weight:
normal" and just leaving it alone.
I would like to be able to remove all instances of a property from the
current selection; I guess there's already a way to do this.
Musing, Frank
On 24 Oct 2004, at 23:17, msevior@physics.unimelb.edu.au wrote:
>> o FV_View: add three new methods:
>> - getAllAttrProp: get all properties associated with current location
>> - queryCharFormat: determine whether a property is specified
>> explicitly
>
> 1. _findBlockAtPosition can return a NULL pointer if the point is
> exactly
> in the wrong position or if the piecetable and layouts are not yet
> fully
> stablized after a manipulation.
>
> 2. Looking up att/props is very expensive. The current code for
> getChar*
> getBlock* getSection* props cache's the current properties for a
> substantial speed up.
Received on Mon Oct 25 10:40:14 2004
This archive was generated by hypermail 2.1.8 : Mon Oct 25 2004 - 10:40:14 CEST