[SOLVED] No info in Object Inspector Information Box lazarus / 9-Editor ---------------------------------------------------------------------- petevick · 2024-01-09 15:47 Soon after I first open the Lazarus IDE I notice that no information is being displayed in the Object Inspector Information Box. Then, after compiling for the first time, if I use Alt+Spacebar to complete code, I get this error Error: unit not found: LCLType I can fix both by opening Options and closing it again. Is there anything I can do to prevent this happening at all, it's becoming a right pain in the rear !! ---------------------------------------------------------------------- vfclists · 2024-01-10 13:30 Quote from: petevick on January 09, 2024, 04:47:57 pmSoon after I first open the Lazarus IDE I notice that no information is being displayed in the Object Inspector Information Box. Then, after compiling for the first time, if I use Alt+Spacebar to complete code, I get this error Error: unit not found: LCLType I can fix both by opening Options and closing it again. Is there anything I can do to prevent this happening at all, it's becoming a right pain in the rear !! Perhaps you should offer more info about your environment - Which versions of Lazarus and FPC and your OS? ---------------------------------------------------------------------- petevick · 2024-01-10 13:36 Quote from: vfclists on January 10, 2024, 02:30:31 pm Perhaps you should offer more info about your environment - Which versions of Lazarus and FPC and your OS? All three are in my signature. ---------------------------------------------------------------------- Josh · 2024-01-10 13:50 i would try 1. Tools->Rescan FPC Source Directory 2. Tools->Configure Build Lazarus (Make sure you tick the box Clean All radio button) the Click Build. The above should refresh everyhing ---------------------------------------------------------------------- petevick · 2024-01-10 14:01 Thanks Josh, I'll try those suggestions.... ---------------------------------------------------------------------- petevick · 2024-01-10 14:22 Quote from: Josh on January 10, 2024, 02:50:27 pmi would try 1. Tools->Rescan FPC Source Directory 2. Tools->Configure Build Lazarus (Make sure you tick the box Clean All radio button) the Click Build. The above should refresh everyhing Unfortunately neither worked.    In Tools->Configure Build Lazarus there was no Clean All option in the Clean up box, only Clean common files, which I ticked. ---------------------------------------------------------------------- Josh · 2024-01-10 18:31 Hi just installed Laz 2.2.0 anf fpc3.2.2 on Mint 21.1 ce as ur sig and i get the clean all option is it possible its hidden from view, have you triedexpanding the window? ---------------------------------------------------------------------- petevick · 2024-01-10 19:58 Quote from: Josh on January 10, 2024, 07:31:46 pmHi just installed Laz 2.2.0 anf fpc3.2.2 on Mint 21.1 ce as ur sig and i get the clean all option is it possible its hidden from view, have you triedexpanding the window? That's going above and beyond Josh  but no, I just get the one option as attached. I've checked a Linux 19.3 x64 VM and a Linux 19.3 x32 VM and they are both the same, just one option, but in a Windows 10 VM it does show the four options as your screenshot. ---------------------------------------------------------------------- JuhaManninen · 2024-01-11 03:24 Quote from: petevick on January 10, 2024, 08:58:10 pm... I just get the one option as attached. That is probably caused by directory access rights. Lazarus installation goes to a read-only directory. A rebuilt Lazarus goes to your local configuration directory (~/.lazarus). StartLazarus knows which executable to run. So, don't run Lazarus binary directly, run StartLazarus binary. As things are broken, it would also be time to update to Lazarus 3.0. It is years ahead of 2.2.0. See also my post about building Lazarus from sources :  https://forum.lazarus.freepascal.org/index.php/topic,65612.msg500244. html#msg500244 It is easy, it prevents issues with read-only directories and it has other benefits. ---------------------------------------------------------------------- petevick · 2024-01-11 07:01 Quote from: JuhaManninen on January 11, 2024, 04:24:23 amThat is probably caused by directory access rights. Lazarus installation goes to a read-only directory. A rebuilt Lazarus goes to your local configuration directory (~/.lazarus). StartLazarus knows which executable to run. So, don't run Lazarus binary directly, run StartLazarus binary. As things are broken, it would also be time to update to Lazarus 3.0. It is years ahead of 2.2.0. See also my post about building Lazarus from sources :  https://forum.lazarus.freepascal.org/index.php/topic,65612.msg500244. html#msg500244 It is easy, it prevents issues with read-only directories and it has other benefits. Thanks for this information. The desktop launcher I use does use the startlazarus %f command. ---------------------------------------------------------------------- Josh · 2024-01-11 10:16 Hi I use fpcupdeluxe to install independent (sandboxed) versions of  fpc/lazaurus in a fully accessable folder ie Home/DevelopmentTools/Laz22 Home/DevelopmentTools/Stable Home/DevelopmentTools/Fixes https://github.com/LongDirtyAnimAlf/fpcupdeluxe/releases/tag/v2.4.0c i'm using intel x86_64 so I use fpcupdeluxe-x86_64-linux I put this in the Relevent Folder of the installation. Remember to right click ->properties and set it as runable/executable, 1) set inistall directory (button top left). to the folderwhere you want to install fpc/laz. 2) Select the FPC/Lazarus version you want to install Click Install When it finishes it creates a destop icon to launch that version ---------------------------------------------------------------------- petevick · 2024-01-11 10:28 Quote from: JuhaManninen on January 11, 2024, 04:24:23 amThat is probably caused by directory access rights. Lazarus installation goes to a read-only directory. A rebuilt Lazarus goes to your local configuration directory (~/.lazarus). StartLazarus knows which executable to run. So, don't run Lazarus binary directly, run StartLazarus binary. As things are broken, it would also be time to update to Lazarus 3.0. It is years ahead of 2.2.0. See also my post about building Lazarus from sources :  https://forum.lazarus.freepascal.org/index.php/topic,65612.msg500244. html#msg500244 It is easy, it prevents issues with read-only directories and it has other benefits. Hi JuhaManninen. I've just tried building from source using the instructions in your post, but when I use git switch fixes_3_0 I get this error - git: 'switch' is not a git command. See 'git --help'. ---------------------------------------------------------------------- petevick · 2024-01-11 14:22 I bit the bullet and updated to Lazarus 3.0. All seems to be working just fine. One benefit are the much nicer icons in the message dialogues. Thanks to all for the help and information, I appreciate it. ---------------------------------------------------------------------- JuhaManninen · 2024-01-11 15:49 Quote from: petevick on January 11, 2024, 11:28:41 amHi JuhaManninen. I've just tried building from source using the instructions in your post, but when I use git switch fixes_3_0 I get this error - git: 'switch' is not a git command. See 'git --help'. OK, then type git checkout fixes_3_0. The switch command in Git is rather new and Mint has old versions of SW. I am now sure why switch was introduced. It works only with branches while checkout also works with commit hash IDs. I figured there is some good reason and I liked the shorter switch, thus I started to use it. I will modify the old post in the link to include checkout command. Quote from: petevick on January 11, 2024, 03:22:11 pmI bit the bullet and updated to Lazarus 3.0. All seems to be working just fine. One benefit are the much nicer icons in the message dialogues.   Cool! ---------------------------------------------------------------------- petevick · 2024-01-12 17:01 Quote from: petevick on January 11, 2024, 03:22:11 pmI bit the bullet and updated to Lazarus 3.0. All seems to be working just fine. One benefit are the much nicer icons in the message dialogues. Thanks to all for the help and information, I appreciate it.  I've since had to fall back to 2.2.6 because 3.0 was causing the main Laz IDE window to jump about if I moved it. The same behavior occurred if I had a form with a lot of controls on it, even the compiled app did behaved the same when moved. On the positive side, I'm no longer experiencing the behavior that I originally had with 2.2.0. ---------------------------------------------------------------------- JuhaManninen · 2024-01-13 06:58 Quote from: petevick on January 12, 2024, 06:01:27 pmI've since had to fall back to 2.2.6 because 3.0 was causing the main Laz IDE window to jump about if I moved it. That may be an interaction between Cinnamon desktop and LCL-GTK2. You should try the other stabile widgetset, LCL-QT5 (or LCL-QT4). Cinnamon may have better support for it. Note: When you run Lazarus 3 compiled from sources directly from its location (./lazarus &), it does not interfere with the installed version. The Lazarus 3 directory is not in the $PATH. You can use --pcp= (--primary-config-path=) parameter to use separate config directories. Eg. ./lazarus --pcp=~/.lazarus3 & ---------------------------------------------------------------------- machinetched · 2024-01-19 11:43 Quote from: petevick on January 12, 2024, 06:01:27 pmQuote from: petevick on January 11, 2024, 03:22:11 pmI bit the bullet and updated to Lazarus 3.0. All seems to be working just fine. One benefit are the much nicer icons in the message dialogues. Thanks to all for the help and information, I appreciate it.  I've since had to fall back to 2.2.6 because 3.0 was causing the main Laz IDE window to jump about if I moved it. The same behavior occurred if I had a form with a lot of controls on it, even the compiled app did behaved the same when moved. On the positive side, I'm no longer experiencing the behavior that I originally had with 2.2.0. This reminds me of a bug I ran into under the Debian Bookworm/Window Maker Live distribution, where the windows jitter as they are being resized and refreshed, eventually settling down and recovering from the jittering. I still use the same installation, albeit on XFCE, where everything is kosher. My bug, however, appeared under the 3.9.9 trunk installation. The same bug occurs, again, on Window Maker when hiding and unhiding all the windows simultaneously through the window manager menu option.