[SOLVED] Feature request: Default hide/show nonvisual components lazarus / 10-Designer ---------------------------------------------------------------------- Hansaplast 路 2025-10-21 09:30 I was wondering if this feature can be added to the IDE options: hide/show nonvisual components. (under setting: IDE options - Envronment - Miscellaneous) There is already the option "Show captions of nonvisual components", so maybe the proper place to have to add the option to hide nonvisual components by default. I always hide the nonvisual components, but I always have to right click the form to hide them with new projects, and after loading a project (this option does not seem to be saved in the project). Please correct me if this already exists. ---------------------------------------------------------------------- n7800 路 2025-10-21 15:35 Yes, I noticed this a long time ago too and wanted to write a patch, but I kept putting it off until I forgot )) Of course, this option should be added to the "Environment > Form Editor" category along with the other Designer options. I don't know if you mentioned project options by accident, but I think it should be implemented only at the IDE level. ---------------------------------------------------------------------- Hansaplast 路 2025-10-21 17:33 I totally agree 馃槉 Haha, like we both said, under setting: IDE options - Environment - Miscellaneous. Either I wrote it a little clumsy or you misread 馃槈 Anywho ... Would be great to have that option though! ---------------------------------------------------------------------- n7800 路 2025-11-11 08:41 I've finished the patch and created a merge request. Let's see what the developers have to say... ---------------------------------------------------------------------- n7800 路 2025-11-11 08:42 There's a small nuance. The option is now available in the Designer context menu and in the IDE Options dialog. What are the interaction variants? 1. Only the setting in the options dialog is remembered. This is the default state for each new Designer. You can change its state separately via the context menu, and it won't be remembered. This is quite flexible. 2. Changes in the context menu are also remembered. This is much more obvious and familiar to the user, and theoretically, the checkbox in the options might not even be necessary. On the other hand, there can be multiple Designers - switching the state in one won't change the others. This means there can be multiple states, but only the most recent switch is remembered. 3. As in the second case, but switching in any Designer will change all the others. This consistent but it's lacks flexibility. Personally I don't have a preference. So far, only the first option is technically implemented. ---------------------------------------------------------------------- Hansaplast 路 2025-11-11 09:00 Very cool! 馃憤馃徎 Option 1 Sounds like the way to go - only remembering the setting in the IDE Options is good enough for me. Changing it in the Designer view is (probably) often just a temporary change - like when one wants to take a quick look at the non-visual controls. I typically hide the non visuals right away and only make them visible when needed, but I can imagine others working the other way around (as it is the way it works right now). 2 and 3 are maybe nice to have, but most certainly not needed on my end. Just my opinion - I'd be super happy with option 1 (as you already implemented) 馃槉 Excited to go test this! Thank you! And congrats on the 200th merge request! 馃槉 ---------------------------------------------------------------------- n7800 路 2025-11-11 23:25 Thanks, MR has been merged and will be in Lazarus 5.0. ---------------------------------------------------------------------- Hansaplast 路 2025-11-12 11:15 Trunk is at 4.99 right now, right? (just seeing how patient I need to be 馃槈) ---------------------------------------------------------------------- JuhaManninen 路 2025-11-12 12:52 Quote from: Hansaplast on November 12, 2025, 12:15:11 pmTrunk is at 4.99 right now, right? (just seeing how patient I need to be 馃槈) You can use Lazarus trunk already. It is stable and usable most of the time. I recommend it for hobby projects. Only if you maintain some critical client app then you should stick with a released Lazarus version. ---------------------------------------------------------------------- n7800 路 2025-11-12 14:50 If you decide to give it a try, use FpcUpDeluxe to install it (I haven't personally used it) or just do it via Git: Code: Bash 聽[Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i git clone https://gitlab.com/freepascal.org/lazarus/lazarus c:\lazcd /d c:\lazecho --pcp=config > lazarus.cfgmake clean bigidelazarus The command in line 3 is needed to create an isolated configuration file (recommended). All settings for this installation will be stored in the "config" subfolder. ---------------------------------------------------------------------- Hansaplast 路 2025-11-12 17:59 I use trunk all the time (through FpcUpDeluxe) 馃槉 Will give it a try! ---------------------------------------------------------------------- Hansaplast 路 2025-11-13 09:31 Works as advertised! Nice! Thanks again n7800, really appreciate it 馃槉