[Libreoffice-ux-advise] [Bug 97906] message "References not found" instead of data sources pane

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=97906

--- Comment #17 from sophie <gautier.sophie at gmail.com> ---
Hi Jay, 
(In reply to Yousuf (Jay) Philips from comment #15)
> I stumbled on the error a few days back and felt it wasnt clear enough and
> thought the message should be improved to better explain why it didnt work,
> as i had the same problem as most in the bug report of not understanding why
> until i created a formula field and then it worked.
> 
> So do i think we should disable the error message? No. I think we shouldnt
> disable the message as its an error message just like when we press F3 in
> writer and their is no AutoText around.
> 
> @Cor, @Heiko, @Stuart: Whats your take?
> 
> As mentioned above, improving the error message language would be good and
> we could also use it as a means of directing people used to the F4 opening
> Data Sources to its new shortcut key. So i propose we change the message to
> something like.
> 
> No references found in the selected cells.
> Use Ctrl+Shift+F4 to open Data Sources.

What sound strange here is indicating two different functions in an error
message, but I agree with you that the error message is necessary to respect
the new design of the F4 shortcut. 
> 
> It would be useful to backport the new shortcut reference part to 5.1, so
> other confused users are aware of the shortcut change. @Sophie: Your
> thoughts?

Ok for the backport, but I'm really not sure about mentioning the Ctrl+shift+F4
in the error message
> 
> Would be good if we could name the dialog title to 'Toggle References' or
> something like that.

+1
> 
> @Maxim: Can we extend ScDocShell::ErrorMessage() so that we can not only
> display text in the dialog but also the dialog title, just like we have in
> LO Basic
> https://help.libreoffice.org/Basic/MsgBox_Statement_Runtime
- Sophie

-- 
You are receiving this mail because:
You are on the CC list for the bug.