https://bugs.documentfoundation.org/show_bug.cgi?id=46579
Tom <tom.kuip...@hetnet.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #31 from Tom <tom.kuip...@hetnet.nl> ---
More information and correction:
Correction: The mentioned workaroud does work but with restrictios, see below.
Other findings:
1. Unlike implemented for push-buttons, no "click-effect" is implemented for
image-buttons. User therefore does not clearly see whether or not a button has
been used.
2. Image-buttons used for navigation are not disabled when not applicable (i.e.
first and previous record buttons are not disabled when record-pointer at first
record of a recordset). This is working correctly when using push-buttons with
a navigation action.
3. When opening a second form without closing the current form, and then using
the first form again, navigation does not work anymore when using
image-buttons. It seems the form has lost its record-pointer.
4. When using image-buttons in combination with a called macro to perform the
required record action everything works correctly, except disabling as
mentioned before.
Used coding in that case:
sFormName = Split(thiscomponent.Title," : ")(1) 'required?
oForm = thisComponent.drawpage.forms.getByName(sFormName) 'required?
oDocument = ThisComponent.CurrentController.Frame
oDispatcher = createUnoService("com.sun.star.frame.DispatchHelper")
oDispatcher.executeDispatch(oDocument ,".uno:FirstRecord","",0,Array())
Interesting finding: if in addition to image-buttons also push-buttons are
defined with action navigation on the form disabling reacts for these buttons
if the image-buttons are used.
I do realize that these issues have mainly a "cosmetic" character, since
push-buttons can be used instead, but the concerned functionality should for
image-buttons either be corrected or not made available.
--
You are receiving this mail because:
You are the assignee for the bug.
