I think it will help for user if there is Object Manager in Libreoffice Draw like in Corel Draw. Because, user will meet difficulty when choose any object.
Hi megasaputra, Thanks for the report. But did you try the Navigator? F5 Every (named) object can be found there... Cheers - Cor
Hi Cheers, The Navigator in Libreoffice Draw is not like in CorelDraw. In Corel, if I select the object, then the object name in object manager is selected too. And the other way, if I select the object name in object manager, then the object will be selected too. I hope, a new LibreOffice Draw will create Navigator like object manager in Corel. Thank you. (In reply to Cor Nouws from comment #1) > Hi megasaputra, > > Thanks for the report. But did you try the Navigator? F5 > Every (named) object can be found there... > > Cheers - Cor
Hi Mega, Double clicking the name in the Navigator does select the object in the document. (in any case the objects visible in the Navigator in Draw, the ones that have a name). What does not work: selecting the object in the document, highlights the name in the Navigator. (It does for Headings, when Content View is activated (second icon on second row) but not for other contents. I'll change the summary of this issue accordingly. (was "Add object manager", is now "Navigator does not select/highlight names of images, objects, tables etc that get focus, also not with Content View activated" OK? Cheers - Cor
Hi Cheers, Ok, I agree. I hope, LibreOffice will be better on the next.
*** Bug 134419 has been marked as a duplicate of this bug. ***
Created attachment 164611 [details] Writer Navigator table, frame, OLE, image and draw objects tracking demo Hi fellow LO enthusiasts, Here is effort that provides for Tables, Frames, Images, OLE objects and Drawing objects to be tracking by the Navigator when selected in the document. https://gerrit.libreoffice.org/c/core/+/101253 Please see attached demo. Comments and code review greatly appreciated :)
(In reply to Jim Raykowski from comment #6) > Here is effort that provides for Tables, Frames, Images, OLE objects and > Drawing objects to be tracking by the Navigator when selected in the > document. Brilliant! Guess it works the other way around as well and by double-clicking the Navigator node you jump to the respective document position. What bothers me is the separation of content, for example the frame goes somewhere and the contained image somewhere else. Wouldn't it be more expectably to keep the natural order with First Chapter Chapter 1.1 <Paragraph 1> Frame 1 Image 1 <Paragraph 2> Table 1 ... Probably not when you look for ImageXY. But I could imagine a choice here... (completely off-topic on this ticket).
In comment made at gerrit patch, Heiko has pointed out a nimbus situation where selection of a frame object in the document results in highlighting of the frame entry in Navigator but double clicking on the frame entry in Navigator moves focus into the frame object in the document and therefore results in frame no longer highlighted in the Navigator. The Navigator frames context menu item 'Go to' moves focus to the document frame. When frame has focus, pressing the enter key moves focus to inside the frame. It seems making double click select the frame is the easy solution to the nimbus.
@Jim, Thanks for working on this bug :-). I'm already exited!
Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/dda71436b8594fb0669b3ac06c02a3997a0674be tdf#95378 Writer Navigator document content tracking It will be available in 7.1.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Resolve as fixed, Jim?
(In reply to Heiko Tietze from comment #11) > Resolve as fixed, Jim? Bookmarks, Sections, Hyperlinks, References, Indexes and Comments still aren't tracked. Maybe what is done is enough to resolve as fixed?
(In reply to Jim Raykowski from comment #12) > Bookmarks, Sections, Hyperlinks, References, Indexes and Comments... Not vital to track everything in extra tickets, IMHO. But may I assign it to you? (In other words: please revert if you don't plan to continue on this)
Dear Jim Raykowski, This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assign it back to yourself if you're still working on this.
Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f11ed86c0ce8b41482ad217bb6700832ef746870 tdf#95378 Writer Navigator: Track sections It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/d62f03d316fb4c60087fc2af626bbd0b35b98693 tdf#95378 Writer Navigator: Track hyperlinks It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/8644a3114d412e8de6cc6712c2f2bcad436906c9 tdf#95378 Writer Navigator: Track references It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/e43eeac1a99ea0d70192dfd7cecf3e8f52f3e53c tdf#95378 Writer Navigator: Track indexes It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/cdc1f41d4530ad3ec553d90dad803bc5b940656c tdf#95378 Writer Navigator: Track bookmarks It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
I believe all content types shown in the Navigator are now tracked.
(In reply to Jim Raykowski from comment #20) > I believe all content types shown in the Navigator are now tracked. Nice! I would be lovely to have this in Draw/Impress too :-). Me preferring 'finishing' this topic ones and (hopefully) for good; consistency and coherence across the board (all modules) It's sometimes pretty frustrating that that code must be adapted for each object, and each module. :-( This likely not limited at the bugreporter side but for developers too. Reporting bugs sometimes feels like complaining: being disrespectful/ not appreciating the effort done, by focusing/nagging on the wrong/incompleteness (instead of the improvement).
(In reply to Telesto from comment #21) > Reporting bugs sometimes feels like complaining: being disrespectful/ not > appreciating the effort done, by focusing/nagging on the > wrong/incompleteness (instead of the improvement). Add this disclaimer to every report to remind us on the importance of your contribution.