I like having the zoom controls on the top of the screen, so I usually add them to the top toolbar. However after they've been added, if Krita is closed and opened anew, the Zoom In/Zoom Out buttons, as well as the Zoom control with slider if it was added, consistently fail to appear. Other added buttons, like Undo/Redo, or canvas rotation, appear normally. The Zoom controls fail to appear regardless of where on the toolbar they are added, or which toolbar they are added to. The provided screenshot depicts the toolbar configuration window open immediately after opening Krita - the Zoom buttons are present in the list, the Apply button is greyed out as no changes were made, but the buttons are not on the toolbar. The missing controls are not off beyond the length of the toolbar. The missing controls do not reappear if the visual style of toolbar items is changed from the drop-down menu (i.e. icons or text). The missing controls reappear if the toolbar configuration window is opened, any action at all is taken there (even i.e. moving the same element up and down again so that the list is the same), and either the Apply button is clicked, or the OK button is clicked when the Apply button is enabled. Reproducible: Always Steps to Reproduce: 1. Add Zoom In or Zoom Out buttons to the top toolbar, or the Zoom control. 2. Close Krita. 3. Reopen Krita and load any image. Actual Results: The top toolbar is missing the added Zoom In, Zoom Out, and/or Zoom controls, until any change is applied via the toolbar configuration window. Expected Results: All controls added to the top toolbar should be visible immediately upon opening Krita. What does Krita have against zoom buttons in the toolbar anyway? :P It doesn't seem to happen with anything else. OS: Windows 8 (not 8.1) x64 Krita version: 2.9.0.1 x64 System: Samsung ATIV Smart PC Pro tablet/UMPC/graphics tablet hybrid with S-Pen stylus. Intel i5 CPU @2x1.7GHz, 4Gb RAM, Intel HD4000 GPU No known performance-altering or "accelerator" software installed that could interfere with the program. Bug has been present since early beta versions of 2.9, as far as I can remember. Not sure if it was there earlier, I wasn't using this setup of controls back then.
Hi Sean, Thanks for your report. I can confirm the issue -- I'm not quite sure where it comes from, but the zoom controls are a bit special because they are tied too closely to the open image, so I guess the items don't get created until you open an image, and then it's too late for Krita to add them to the toolbar.
*** Bug 347424 has been marked as a duplicate of this bug. ***
(In reply to Boudewijn Rempt from comment #1) > Hi Sean, > > Thanks for your report. I can confirm the issue -- I'm not quite sure where > it comes from, but the zoom controls are a bit special because they are tied > too closely to the open image, so I guess the items don't get created until > you open an image, and then it's too late for Krita to add them to the > toolbar. As i mentioned in my duplicate-report, this happens with all the brush, transform and selection tools as well. Others like "mirror view" and "erase mode" are unaffected. Going into "configure toolbars" and doing an "apply" will bring them back. There has to be something these tools have in common to make them disappear...
It's the buttons for things that are created once we create an image that are broken.
*** Bug 345529 has been marked as a duplicate of this bug. ***
*** Bug 348741 has been marked as a duplicate of this bug. ***
Same behaviour for the "Brush smoothing" buttons for me ... Before opening the first document, they are missing in the configuration list and in the toolbar... After opening it, they are appearing in the configuration list, but not in the toolbar... Please see screenshots attached.
Created attachment 93300 [details] Missing buttons int he toolbar before opening a new document
Created attachment 93301 [details] Missing buttons in the toolbar after opening a new document
*** Bug 350646 has been marked as a duplicate of this bug. ***
*** Bug 349501 has been marked as a duplicate of this bug. ***
*** Bug 358093 has been marked as a duplicate of this bug. ***
Fixed in 3.1.2