[libreoffice-users] Re: panel in open and save as dialogues
On 30/09/14 22:30, Steve Edmonds wrote: I just noticed in my dolphin at top right settings I can show tree view. Steve Yes, in dolphin you can, but not in Libreoffice itself; the view there is only of 'Places' John On 2014-09-28 04:38, John King wrote: On 27/09/14 16:00, Jean-Francois Nifenecker wrote: Le 27/09/2014 11:19, John King a écrit : Libreoffice 4.2 and 4.3 on opensuse and xubuntu The left hand panel in the 'open' and 'save as' dialogues shows 'Places' This is a LibreOffice dialog, an alternative to the system dialogs. Thanks for the suggestion, but No, this is the system dialogue. The libreoffice dialogue selection in Tools-Options-General is unchecked. My left hand panel is headed 'Places', and underneath is listed Search, Recently used, what looks like various devices, and then places that I've defined. The + and - buttons only operate on the places section. If I select to use libreoffice dialogues, then I only see places I've defined, which are not necessarily the same as the ones defined in the system dialogue. Is it possible to change this to show the folder/directory tree instead, as in dolphin and nautilus? Yes, it is. Go to the Tools Options menu then LibreOffice General. Uncheck the Use LibreOffice dialogs checkbox. See above comment It would make it much easier to navigate through several layers of folders. Yes, perhaps. Note that the LibreOffice dialogs are (IMO) providing a better UI: the Places thingy allows to always have the more often used directories at hand (too bad they are not sorted), which is a PITA when using the native dialogs. Second, the LO dialogs provide a Connect to server button (the three dotted button, top right) which makes very easy to connect to... well... a server :) To add or delete an often used directory to the Places list, just use the + and - buttons at the bottom. HTH, I agree that the libreoffice dialogues are very useful for connecting across the network, and I use them extensively for that. However, I would like the option of being able to move up/down a directory tree rather than having to do multiple clicking to search through one directory layer at a time. John -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Re: zoom in and out bound to a key
Mark == Mark Bourne libreoffice-ml.mbou...@spamgourmet.com writes: A couple of possibilities... Thanks for your answer. 1. Your operating system might do something with those shortcut keys, and not pass them on to LibreOffice. Other shortcut keys I have set work fine (I am on Linux Kubuntu 10.04) If the same shortcut key is defined for both, the one for an individual application takes priority when in that application. In Writer, Ctrl++ is assigned to Calculate and Ctrl+- is assigned to Optional hyphen (at least for me). If you assign those keys to zoom in and out at the LibreOffice level, they will not have that effect when in Writer; you'd need to remove the assignments from the Writer level (and likewise for Calc etc. If you want them to work there too). I know, and that is why I tried out other bindings such has Alt+F2 and it does not work neither, I googled around and found out that it/was a long standing bug, that is zoom in and out cannot be bound to a key! I am using LO 4.2. Did you try it out, successfully? If so which version do you use, because I then might upgrade. Uwe -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: How to handle regressions
Than you *very* much for the excellent and detailed explanation. That clears up a lot of things for me about the process. Follow-up... In the bug UI, is there an easy way to get a list of bugs that have been patched/fixed in master, that a user like me could browse, and pick certain ones that I could then test and if confirmed fixed, could request be back-ported (if they haven't been already)? I would be very happy to participate in this manner, but honestly, the bug UI is a bit daunting, so anything that makes this easier for non devs would be very welcome for technically inclined non-devs like yours truly. Thanks again for taking the time to explain this so clearly. On 10/3/2014 8:26 PM, V Stuart Foote vstuart.fo...@utsa.edu wrote: @Charles, *, Tanstaafl wrote Also, I'm confused... Jan-Marek in the bug comment on August 17th - well before the 'Hard code freeze' on September 1st for 4.3.2 (released on Sept 22nd - said that the patch would show up in the daily builds after that. So, I'm not complaining, I'm just asking - can someone who understands the dev process explain why this fix did not make it into 4.3.2? No worries, it can get a bit confusing about what commits are where and when. His would show up in the daily builds refereed only to master branch. To be clear, in the normal flow of things, majority of development is made by commits onto the master branch. That includes new features, or UX/UI tweaks or even patches to repair or revert regressions. The in-line field edits have been available for testing in master since the commit in August. So where it gets confusing is the master's relationship with prior releases. At present we have the 4.2 branch nearing its final bug-fix release and then EOL a month later, and the 4.3 branch with its third bug fix in the works. While commits to master can and do break things, in order to keep the code stable, patches committed to master require additional review and deliberation before being back-ported to a prior branch. As needed some work will be done directly on the older branches--but most is integrated into master first and ideally are fully tested there. Some times if dealing with an obvious regression with simple correction, the developer will put up the back-port for review immediately, but usually just one release back. At times the issue has technical dependencies and requires review and validation, and only then will the back-port be posted and again reviewed before it is committed. But occasionally the dev will simply overlook a good opportunity to resolve an issue on branches other than master--which is understandable as most developers are forward looking and framing the work to tackle the next feature or issue in queue. And that is where the user and QA community comes in, we have to stay up with the issues on the forum and in BZ and occasionally make comment regards opportunity that might otherwise be missed. For this issue--despite being on the 4.2 Most Annoying Bug list--once patched the back-port to 4.2 or to 4.3 for the in-line field editing was not pursued. In fact it was only proposed yesterday, meaning it missed 4.3.2 testing and build cycle. But when committed to the branch should make the 4.3.3 bug-fix cut. And, technically, it could still make the 4.2.7 final release, but that requires an exceptional approval by three devs or the Engineering Steering Committee. Jan-Marek G.'s proposed backport to 4.3 branch for the in-line field edits are up for code review, each of these is a separate facet of the patch needed for 4.3 (and possibly 4.2) as already implemented in master since August. https://gerrit.libreoffice.org/11779 https://gerrit.libreoffice.org/11780 https://gerrit.libreoffice.org/11781 https://gerrit.libreoffice.org/11782 If there are no technical issues, since the patch put into master in August was sound they'll likely be approved and committed in time for the next 4.3 release--but available for testing in context on nightly builds of the 4.3 branch once committed, i.e. they should be checked by users and QA for continued proper function. Hope that was clear enough for all. Stuart -- View this message in context: http://nabble.documentfoundation.org/How-to-handle-regressions-tp4124391p4124855.html Sent from the Users mailing list archive at Nabble.com. -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Re: MySQL native connector for LibreOffice 4.2 and 4.3 (Linux versions)
Le 04/10/2014 00:09, Heinrich Stöllinger a écrit : Heinrich, Dan, It is a known limitation of the native mysql connector, although I don't remember right now whether an enhancement request has been filed. I couldn't find one after a quick search on bugzilla. Alex -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Understanding the Bugzilla issue tracker
Charles S. (aka. Tanstaafl) asked in this thread: Sent: Saturday, October 04, 2014 7:07 AM Subject: Re: [libreoffice-users] Re: How to handle regressions Follow-up... In the bug UI, is there an easy way to get a list of bugs that have been patched/fixed in master, that a user like me could browse, and pick certain ones that I could then test and if confirmed fixed, could request be back-ported (if they haven't been already)? I would be very happy to participate in this manner, but honestly, the bug UI is a bit daunting, so anything that makes this easier for non devs would be very welcome for technically inclined non-devs like yours truly. @Charles, *, Great question! As it happens you can do just that as the project has implemented use of a set of status messages posted to the *Whiteboard* field in Bugzilla to hold various QA and development status notes. Notice of patch commits against specific BZ issues are automatically posted** -=To search against the Whiteboard=- Open Bugzilla -- Search, and select the Advanced Search panel tab Under the Product column select LibreOffice Under the Status column keep the default of NEW-ASSIGNED-REOPENED (unless looking at historical details) In the Detailed Bug Information section, on the Whiteboard row enter target:4.4.0 (i.e. either current master, or specific branch) The general and advanced details are in these two Wiki articles: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Whiteboard https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Whiteboard/Advanced =-=-= From the Complete List of Accepted Whiteboard Tags https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Whiteboard/Advanced#Complete_List_of_Accepted_Whiteboard_Tags *target* Description: target refers to the version(s) where a commit which fixes the problem can be expected to be seen. Use: Generally “target” is automatically entered when a developer commits a patch specifically to fix a bug reported on the bug tracker. Users, QA and Developer should generally not manually enter “target” into whiteboard, the only exception is when the automatic system did not tag the bug and a developer or QA member knows the exact commit which fixed the bug and what version of LibreOffice will see the patch. In these cases a QA member can mark a bug as “target:x.x.x.x” where x.x.x.x is the version(s) of LibreOffice where the commit was pushed to. *Example:* target:4.2.0.0 This means that a commit which fixes the problem was committed to the 4.2.0.0, and therefore if a user or QA member tests 4.2.0.0 they should not see the bug any longer. =-=-= Looking at Bugzilla and the Wiki, the whole process is a little daunting, but really can be quickly mastered. A good starting point for the QA process--this Wiki page is helpful: https://wiki.documentfoundation.org/QA/BugTriage#Introduction Stuart **Generating the automatic target:xx.xx.xx tag does require that the dev working in git/gerrit annotate the bug being addressed, a manual action so it is not 100%. But, well structured BZ issues facilitate both the QA triage on intake and tracking at all stages as devs work on issues--so the preferred workflow is to capture details into BZ. -- View this message in context: http://nabble.documentfoundation.org/Understanding-the-Bugzilla-issue-tracker-tp4124888.html Sent from the Users mailing list archive at Nabble.com. -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Problem with conditions in fields
Hello, I am having problems with conditions in fields, which I already desribed by the bug report #84290. In short: When printing labels, I want to add my sender address in the first line. But this line shall only be shown for the selected data records, not on the remaining labels of the page. I tried a hidden text field with conditions like !Name, Name == , Name == || !Name. This did not solve my problem. Even changing the field name to [databasename.tablename.Name] brought no change. So if the developers have the opinion that this is not a bug, could you please offer a method to achieve what I am intending. Thank you in advance, Carlo -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Daily Master 64bit deb Install Failure
Hello, I'm using debs from http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@46-TDF/current/ on Ubuntu 14.04 64bit LO 4.2.6, 4.3.2 and the installs have been failing regularly (every weekend or so) for the past two-three months. Package lodevbasis4.4-core05 is always missing. ( see dpkg -i *.deb excerpt below) /dpkg: error processing package lodevbasis4.4-extension-pdf-import (--install): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of lodevbasis4.4-extension-report-builder: lodevbasis4.4-extension-report-builder depends on lodevbasis4.4-core05 (= 4.4.0.0.alpha0); however: Package lodevbasis4.4-core05 is not installed. lodevbasis4.4-extension-report-builder depends on lodevbasis4.4-core05 (= 4.4.0.0.alpha0-1); however: Package lodevbasis4.4-core05 is not installed./ Debs */lodevbasis4.4-core01_4.4.0.0.alpha0-1_amd64.deb/* to */lodevbasis4.4-core07_4.4.0.0.alpha0-1_amd64.deb/* are present in the archive, but */lodevbasis4.4-core05_4.4.0.0.alpha0-1_amd64.deb/* is not. 4.2 and 4.3 releases have installed fine. Any suggestions? TIA - Ubuntu 14.04 64bit : LibreOffice: 4.2.6.2, 4.3.1.1 -- View this message in context: http://nabble.documentfoundation.org/Daily-Master-64bit-deb-Install-Failure-tp4124903.html Sent from the Users mailing list archive at Nabble.com. -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Problem with conditions in fields
Hi :) I dunno a good answer to this. Maybe someone else on the list will come up with something better. In the meantime maybe one of the chapters in documentation might help; https://wiki.documentfoundation.org/Documentation/Publications Maybe the Writer Guide chapter 11, Mail Merge. The more obvious choices are chapters 14 and 15 about Fields and Forms. Apols and regards from Tom :) On 4 October 2014 20:35, Karl Hans Käse-Kaßbaum k.h.ka...@t-online.de wrote: Hello, I am having problems with conditions in fields, which I already desribed by the bug report #84290. In short: When printing labels, I want to add my sender address in the first line. But this line shall only be shown for the selected data records, not on the remaining labels of the page. I tried a hidden text field with conditions like !Name, Name == , Name == || !Name. This did not solve my problem. Even changing the field name to [databasename.tablename.Name] brought no change. So if the developers have the opinion that this is not a bug, could you please offer a method to achieve what I am intending. Thank you in advance, Carlo -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to- unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Re: Daily Master 64bit deb Install Failure
ponsiarceds wrote Package lodevbasis4.4-core05 is always missing. This has been reported as https://bugs.freedesktop.org/show_bug.cgi?id=82288 -- View this message in context: http://nabble.documentfoundation.org/Daily-Master-64bit-deb-Install-Failure-tp4124903p4124914.html Sent from the Users mailing list archive at Nabble.com. -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
