To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=98973
User fs changed the following:
What |Old value |New value
================================================================================
Target milestone|OOo 3.2 |OOo 3.x
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Mon Sep 7 18:40:52 +0000
2009 -------
okay, we might need to discuss what is needed here. What I implemented is that
the events which are offered in the property browser or a table control column
actually work. This affects all events for all column types, a lot of them
simply were never implemented. That is how I had understood the summary of the
issue.
However, the events only work in an *active* editable table cell, which has two
consequences:
First, if you bind a macro the the "mouse button down" event, and then click
with the mouse into a previously inactive cell, then this won't fire the event.
Only after the cell has been activated, and you click into it, again, then the
event is fired, and the macro is called.
Second, if the control does not allow editing cells, then no events are fired at
all, since the controls used for editing are responsible for firing the events.
In both cases, this might not be expectation conformant.
fs->sos: My question to you is: How exactly does your scenario look like? What
events *exactly* is your application interested in?
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
