Hi John,
D John Anderson wrote:
Did you fix the mini calendar size so that it shows only one month? I
think that is the correct fix for this problem. I suspect that this
problem was caused by the fact that the new collection was partially
obscured by the minicalendar, not that the UI changed in a way that
made old mouse positions invalid.
That's what I did: move the divider down so to show only one month.
Actually, 2 recently introduced changes conspire to push the new
collection under the divider:
- the introduction of new OOTB events, making the preview list bigger
- the reduction of the height of the app
It just happened that I'm the committer of both changes (strangely
enough), so I've been made sensitive to the issue. You're right to say
that the UI didn't change but the context (i.e. presence of new OOTB
events and default size) did and that was enough to break the script.
I don't think the script recording depends too much on mouse position
-- most of the events don't use mouse position, even though the
position is recorded and you may see it in the script. There may be a
few exceptions, but they are usually easy to fix. For example, we can
easily use row number instead mouse location for selecting items in
tables (e.g. the sidebar).
You're certainly correct. In the case of the divider capture though, it
seems to be strictly based on mouse coordinate and records the mouse
down and up. There could be a better way of doing it but that's what the
recorder gave me on Mac. You may want to look at that (it's only 2 lines
of added script).
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
