The menu item "Paste" doesn't get disabled if clipboard contains something other than string (Paste button enabled/disabled properly on the panel,) To reproduce, copy an image to clipboard and compare the Paste button and the menu item Paste (the last one is still enabled)
clio: Thank you! Could also let us know if you find some similarity in this set of Basic IDE bugs, please? _Probably_ all these are symptoms of one problem? Would it be possible for you to dig more, please? Thanks a lot!
(In reply to comment #1) > _Probably_ all these are symptoms of one problem? Yes, I think there is a general problem with Basic IDE. > Would it be possible for you to dig more, please? I tried to play with http://www.openoffice.org/issues/show_bug.cgi?id=108119 with LibO code, but IMHO this problem is a lot harder than editing a few lines. So far, I have no idea what is the problem, but I am going to try again, but please note that I am weak in programming, so it can be very hard for me to fix this.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
I can confirm that the paste menu item doesn't get disabled like the paste button. Taking this one.
No call for pasting images in BASIC code, but people will want to be able to put their logo on their dialogs. Not clear at all if there is a bug here greater than Paste should be disabled with non-text on clipboard when Dialog Editor is not visible. Needs more testing to see how the various permutations of Paste enabling goes now.
I ask the assignee to reassign the bug to the default assignee and change its status accordingly if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO