To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=78747
------- Additional comments from [EMAIL PROTECTED] Thu Jun 21 11:13:01 +0000 2007 ------- So - ! - wrt. a fix :-) for my layout code, my preferred way is to export the VCL semantic (as far as possible) identically via the UNO interface. This is in order to provide equivalent functionality via a VCL-like C++ API to help port code fast, so we have: original-OO.o-code -> C++-VCL-like-api -> awt::UNO -> vcl Of course - in order to do that, we need to expose this semantic too. Thus - my proposed fix would be: * in 'VCLXButton::addActionListener' - connect a 'dummy' (NOP) ClickHdl callback, and in removeActionListener - remove it if no other listeners. This would allow the 'OKButton' to fulfill it's traditional role (if no listener was added) and to behave like a normal OKButton if one was - ie. best of all worlds :-) Would you accept that patch [ yes, I didn't write it, and it's a patch-bug - but it's a trivial fix ;-) ] ? - I'd also like to audit all other VCL code-paths to see if there are other conditionals on Links, and attempt to emulate their behavior in a similar fashion - is that ok ? How does that impact basic forms & in-sheet objects etc. - do we expose Ok vs. Cancel vs. Help buttons there anyhow ? and how does it affect (if at all) the model-view UnoControl world ? Thanks guys. --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
