How to Installation Lazarus 2.2.0 on linux mint? lazarus / 1-Linux ---------------------------------------------------------------------- Rama Can · 2022-03-22 14:05 How to installation on Linux mint? I always have problem when I install latest Lazarus on Linux Mint, can anyone help me with this for my college assignment before I install, I first uninstalled Lazarus version 2.0.6 then download fpc-laz_3.2.2_amd64.deb fpc-src_3.2.2_amd64.deb lazarus-project_2.2.0-0_amd64.deb then i run this command in terminal Quotesudo dpkg -i fpc-laz_3.2.2_amd64.deb sudo dpkg -i fpc-src_3.2.2_amd64.deb sudo dpkg -i lazarus-project_2.2.0-0_amd64.deb then get wrong Quotedpkg: regarding fpc-laz_3.2.2_amd64.deb containing fpc-laz:  fpc-laz conflicts with fp-compiler   fp-compiler:amd64 (version 3.0.4+dfsg-23) is present and installed.   fp-compiler-3.0.4:amd64 provides fp-compiler and is present and installed. dpkg: error processing archive fpc-laz_3.2.2_amd64.deb (--install):  conflicting packages - not installing fpc-laz Selecting previously unselected package fpc-src. dpkg: regarding fpc-src_3.2.2_amd64.deb containing fpc-src:  fpc-src conflicts with fpc-source   fpc-source-3.0.4 provides fpc-source and is present and installed. dpkg: error processing archive fpc-src_3.2.2_amd64.deb (--install):  conflicting packages - not installing fpc-src dpkg: warning: files list file for package 'dbconfig-common' missing; assuming package has no files currently installed (Reading database ... 412251 files and directories currently installed.) Preparing to unpack lazarus-project_2.2.0-0_amd64.deb ... Unpacking lazarus-project (2.2.0) ... dpkg: dependency problems prevent configuration of lazarus-project:  lazarus-project depends on fpc-laz (= 3.2.2); however:   Package fpc-laz is not installed.  lazarus-project depends on fpc-src (= 3.2.2); however:   Package fpc-src is not installed. dpkg: error processing package lazarus-project (--install):  dependency problems - leaving unconfigured Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu2) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for gnome-menus (3.36.0-1ubuntu1) ... Processing triggers for desktop-file-utils (0.24+linuxmint1) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for shared-mime-info (1.15-1) ... Processing triggers for man-db (2.9.1-1) ... Errors were encountered while processing:  fpc-laz_3.2.2_amd64.deb  fpc-src_3.2.2_amd64.deb  lazarus-project ---------------------------------------------------------------------- nouzi · 2022-03-22 14:24 First remove old version 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 apt remove fpc-laz*apt remove lazarus*apt autoremove &&  apt clean  and try again ---------------------------------------------------------------------- Rama Can · 2022-03-22 14:49 still with the same error ---------------------------------------------------------------------- Thaddy · 2022-03-22 16:40 Not remove, but purge. ---------------------------------------------------------------------- Rama Can · 2022-03-22 16:48 still with the same error ---------------------------------------------------------------------- bytebites · 2022-03-22 17:07 fp-compiler-3.0.4:amd64 still exists. apt-remove  fp-compiler-3.0.4:amd64 ---------------------------------------------------------------------- Thaddy · 2022-03-22 17:35 apt  purge or apt-get purge if I was not clear. Apt needs to remove <~/home/user> as well. it also needs to remove a config file at /etc Simply calling remove is an error. Only purge removes almost everything. (almost: installation logs) ---------------------------------------------------------------------- Handoko · 2022-03-22 18:10 This is how I totally uninstall and remove the leftovers of the Lazarus installation on Ubuntu Mate: 01. Uninstall lazarus, fpc, fpc-src 02. Delete ~/.lazarus, except: editoroptions, environmentoptions 03. Delete /etc/fp.* 04. Delete /usr/share/fpcsrc 05. Delete /usr/lib/fpc 06. Delete /usr/bin/ppc* Because I want to keep some Lazarus IDE settings so I do not delete the editoroptions and environmentoptions. ---------------------------------------------------------------------- dbannon · 2022-03-22 22:41 A few comments. Firstly, there 'should' be no reason other than mixed install models, why you need to uninstall/purge/nuke a previous install of fpc / lazarus.  Apt will overwrite everything it needs as long as the package name and contents names match. Thaddy - purge does not remove content in $HOME If installing a new Lazarus, even using a different model, Lazarus will detect and update the files in .lazarus if thats where your config goes. So, useful to make a clean start but not essential to nuke .lazarus even. If you have had an old install, perhaps you are using Linux Mint based on the quite old Ubuntu 18.04 for example and then try and install the official ones from FPC/Lazarus then yes, vital you remove all existing FPC/Lazarus files at an operating system level. Apt 'should' be able to do it and purge is a good idea because it will remove config files (under /etc and /usr) as well. You can use apt purge even after a package has been 'removed'. Worth checking that $HOME/.fpc.cfg does not exist but its unlikely. Finally, and very importantly, do not use dpkg to install packages. Its a low level tool called by other programs. Use apt (preferably not apt-get) because it will resolve dependencies (on all recent linuxes) and does do some sanity checking.  gdebi is a nice GUI if you prefer that sort of thing. But not dpkg. So, take home message, trust apt unless you have been mixing install models. Davo PS : consider building Lazarus from source instead of from a deb. Especially on Linux ! https://wiki.freepascal.org/Installing_Lazarus ---------------------------------------------------------------------- Rama Can · 2022-03-24 07:41 so how to fix broken lazarus package? I use the command Quotesudo apt install ./fpc-laz_3.2.0-1_amd64.deb  ./fpc- src_3.2.0-1_amd64.deb  ./lazarus-project_2.0.12-0_amd64.deb *sorry if my english is not good ---------------------------------------------------------------------- Handoko · 2022-03-24 07:56 If you have Lazarus installed previously, try to totally remove the previous installation, see reply #7. Gdebi and Synaptic Package Manager can be helpful if you have problem installing Lazarus on Linux. Also this thread have the information why the installation may failed on Ubuntu and its variants: https://forum.lazarus.freepascal.org/index.php/topic,41524.0.html ---------------------------------------------------------------------- dbannon · 2022-03-24 08:10 ramacan, looks like you have an existing install of 2.0.6 there, that must be quite old. A couple of people mentioned that an old broken install will cause you problems. So, lets see if we can remove it, the fact that its not being taken care of by the install of the new one says its, somehow broken, maybe you removed some bit manually rather than using apt ?  Or installed from source ?  In future, better to use apt to remove anything installed with apt. Anyway, your FPC is probably fine so leave it alone. Try these commands for interest sake  - Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i which lazarus which startlazarus Now, lets get rid of ALL lazarus - 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 apt purge lazarus which lazarus which startlazarus If the second "which" commands gave us a result, you still have something there and apt does not know about it. So, I am afraid, you need to, as root, manually remove it. Only do this AFTER you have tried to remove lazarus with the apt command and failed.  Please be very careful. 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 sudo rm -Rf  /usr/lib/lazarus   /usr/bin/lazarus Now, try those "which" commands again, if you get a response, please copy the result here and we'll have another think. Maybe run these commands and post the result - Code: [Select]ls -l /etc/fpc.cfg ls -l ~/.fpc.cfg ls -l /usr/bin/laz* Only when we are sure we don't have any residual broken Lazarus left should you try again to install the new one.  We may need to deal with some symlinks in /usr/bin ... Don't worry ramacan, we will sort it out !  And your English is fine. Davo ---------------------------------------------------------------------- Rama Can · 2022-03-24 10:01 I've done the command above, then what else? is it time to install again? Quoteram@ram-4G:~$ sudo sh -c "rm -Rf /etc/fp.* \ > rm -Rf /usr/share/fpcsrc \ > rm -Rf /usr/lib/fpc \ > rm -Rf /usr/bin/ppc*" [sudo] password for ram:          ram@ram-4G:~$ apt purge lazarus Reading package lists... Done Building dependency tree      Reading state information... Done Package 'lazarus' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded. ram@ram-4G:~$ which lazarus ram@ram-4G:~$ which startlazarus ram@ram-4G:~$ sudo rm -Rf  /usr/lib/lazarus   /usr/bin/lazarus ram@ram-4G:~$ ls -l /etc/fpc.cfg ls: cannot access '/etc/fpc.cfg': No such file or directory ram@ram-4G:~$ ls -l ~/.fpc.cfg ls: cannot access '/home/ram/.fpc.cfg': No such file or directory ram@ram-4G:~$ ls -l /usr/bin/laz* ls: cannot access '/usr/bin/laz*': No such file or directory ram@ram-4G:~$ ---------------------------------------------------------------------- dbannon · 2022-03-25 00:20 Er, the first line you have posted there was definitely NOT suggested by me. Why on earth have you removed fpc ? I will labour the point a bit here because its important that you understand what just happened. I said " your FPC is probably fine so leave it alone. ".   I wonder if you have not got the idea that fpc and lazarus are two separate things ? You probably had a good fpc install but now you have done the one thing I warned you against, removing components manually that were installed by apt. Now you have a broken fpc install as well as a broken lazarus ! So, some more cleaning up will be necessary. Just how easy that is will depend on the version of apt that your system has. Some versions seem happy to clean up and others not and I have not worked out what the difference is ! So, as a starting point, lets see if your version of apt will still play with us, run this to see if apt still thinks it has fpc or lazarus somewhere, run them one at a time so we can see which does what  - 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 dpkg -l | grep fpc dpkg -l | grep lazarus If either respond (and I expect at least fpc will), you should try and remove them, you may need the force option. Again, do it in this order ! 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 sudo apt purge lazarus sudo apt purge fpcsrc sudo apt purge fpc The lazarus one, at least should tell us that lazarus is not installed, no problems, keep going. If you see a message about not being able to remove something, or the need to "fix" a package, better stop and post the message here. If these ran OK, then you you should do a normal - 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 sudo apt update sudo apt upgrade to make sure your apt database is not damaged. If its not, you should consider yourself very lucky ! Now, if things still look OK, type the following - 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 ls -l /usr/lib/x86_64-linux-gnu/fpc   Assuming you are using a 64bit machine.  And .. 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 ls -l /usr/lib/lazarus ls -l /usr/lib/lazarus You should get no response from all three of the above commands. If you do see something, then you will again have to manually remove that content BUT ONLY if you cannot remove it with apt - that is a golden rule, never ever remove something manually that you can remove with apt ! If you get through all of that and can get no response to the three "ls" commands above, then and only then, proceed to reinstall the deb files you have.  I strongly recommend you install them one at a time so you can clearly see any errors. So, move to the dir you downloaded the debs from and make sure they are there  - 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 cd ls -l *.deb// all good ?sudo apt install ./fpc- laz_3.2.2_amd64.deb // look for any error messages !sudo apt install ./fpc-src_3.2.2_amd64.deb// look for any error messages !sudo apt install ./lazarus-project_2.2.0-0_amd64.deb// look for any error messages ! note the "./" in front of the debs, most important otherwise apt will try and find them in its own databases. the "./" says "these deb files right here in this dir". Davo PS. All these problems do relate, IMHO, to installing Lazarus from a deb. Life is so much easier if you install Lazarus from source code. You do not install it, just keep it in your home dir where you can remove it, replace it or add to it whenever you like. I sometimes wonder if the Lazarus developers should refuse to make a deb package ! ---------------------------------------------------------------------- PierceNg · 2022-03-25 03:41 Quote from: dbannon on March 25, 2022, 01:20:18 amPS. All these problems do relate, IMHO, to installing Lazarus from a deb. Life is so much easier if you install Lazarus from source code. You do not install it, just keep it in your home dir where you can remove it, replace it or add to it whenever you like. I sometimes wonder if the Lazarus developers should refuse to make a deb package ! +1 When I started using Lazarus, I clicked on 'clean up and rebuild all' in a project out of curiosity and got lots of error messages about unwriteable files, because those files, as installed via the deb package, which Lazarus expects to be able to overwrite as and when, are in 'system' locations owned by root.  The deb package of Lazarus may be Linux-friendly (according to the people who make up such rules) but I found it to be programmer- unfriendly, especially when the programmer is new to Lazarus. ---------------------------------------------------------------------- Rama Can · 2022-03-25 07:00 Command as above Quoteram@ram-4G:~$ dpkg -l | grep fpc ii  fpc-laz                                    3.2.2                                    amd64        Free Pascal Compiler ii  fpc-src                                    3.2.2                                    amd64        Free Pascal Sources ram@ram-4G:~$ dpkg -l | grep lazarus rc  lazarus-ide-2.0                            2.0.6+dfsg-3                   amd64        IDE for Free Pascal - common IDE files rc  lazarus-project                            2.2.0                               amd64        RAD tool for freepascal rc  lazarus-src-2.0                            2.0.6+dfsg-3                    all              IDE for Free Pascal - LCL source code ram@ram-4G:~$ sudo apt purge lazarus [sudo] password for ram:          Reading package lists... Done Building dependency tree      Reading state information... Done Package 'lazarus' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded. ram@ram-4G:~$ sudo apt purge fpcsrc Reading package lists... Done Building dependency tree      Reading state information... Done E: Unable to locate package fpcsrc ram@ram-4G:~$ sudo apt purge fpc Reading package lists... Done Building dependency tree      Reading state information... Done Package 'fpc' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded. ram@ram-4G:~$ ls -l /usr/lib/x86_64-linux-gnu/fpc ls: cannot access '/usr/lib/x86_64-linux-gnu/fpc': No such file or directory ram@ram-4G:~$ ls -l /usr/lib/lazarus ls: cannot access '/usr/lib/lazarus': No such file or directory then move to directory /Downloads/lazarus/ Quoteram@ram-4G:~/Downloads/lazarus$ ls -l *.deb -rw-rw-r-- 1 ram ram  39280196 Mar 21 18:35 fpc-laz_3.2.2_amd64.deb -rw-rw-r-- 1 ram ram  30635206 Mar 21 18:35 fpc- src_3.2.2-210709_amd64.deb -rw-rw-r-- 1 ram ram 123714892 Mar 21 18:36 lazarus- project_2.2.0-0_amd64.deb ram@ram-4G:~/Downloads/lazarus$ sudo apt install ./fpc- laz_3.2.2_amd64.deb [sudo] password for ram:          Reading package lists... Done Building dependency tree      Reading state information... Done Note, selecting 'fpc-laz' instead of './fpc-laz_3.2.2_amd64.deb' fpc-laz is already the newest version (3.2.2). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ram@ram-4G:~/Downloads/lazarus$ sudo apt install ./fpc- laz_3.2.2_amd64.deb Reading package lists... Done Building dependency tree      Reading state information... Done Note, selecting 'fpc-laz' instead of './fpc-laz_3.2.2_amd64.deb' fpc-laz is already the newest version (3.2.2). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ram@ram-4G:~/Downloads/lazarus$ sudo apt install ./lazarus- project_2.2.0-0_amd64.deb Reading package lists... Done Building dependency tree      Reading state information... Done Note, selecting 'lazarus-project' instead of './lazarus- project_2.2.0-0_amd64.deb' The following NEW packages will be installed:   lazarus-project 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. After this operation, 848 MB of additional disk space will be used. Get:1 /home/ram/Downloads/lazarus/lazarus-project_2.2.0-0_amd64.deb lazarus-project amd64 2.2.0 [124 MB] Selecting previously unselected package lazarus-project. dpkg: warning: files list file for package 'dbconfig-common' missing; assuming p ackage has no files currently installed (Reading database ... 425156 files and directories currently installed.) Preparing to unpack .../lazarus-project_2.2.0-0_amd64.deb ... Unpacking lazarus-project (2.2.0) ... Setting up lazarus-project (2.2.0) ... Processing triggers for shared-mime-info (1.15-1) ... Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu2) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.24+linuxmint1) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for gnome-menus (3.36.0-1ubuntu1) ... Processing triggers for man-db (2.9.1-1) ... W: Repository is broken: lazarus-project:amd64 (= 2.2.0) has no Size information error that occurs when ./lazarus-project_2.2.0-0_amd64.deb QuoteW: Repository is broken: lazarus-project:amd64 (= 2.2.0) has no Size information ---------------------------------------------------------------------- dbannon · 2022-03-25 08:35 Sigh .... I should have been clearer I guess.  Ram, when you used the dpkg commands, it showed you that apt thinks it has  fpc-laz, fpc-src, lazarus-ide-2.0, lazarus-project and lazarus-src-2.0. Unfortunately, you have removed some or all of the files associated with those packages, manually, with the rm command. So, you should not have proceeded until you cleaned up that situation. I should have mentioned that the actual package names vary depending on where they origionally came from, thats why the dpkg -l command to determine the actual names for you to use in the "sudo apt purge " I am afraid you need to remove them, one by one, in reverse order until the dpkg -l | grep commands return nothing. Please do not proceed with installing until you have removed the broken ones. And, again, I should have been clearer, when installing, I said to check for error messages, I should have added, do not proceed if you get an error message.  Generally, when someone gives you a set of instructions, step by step, you should stop when one step fails !  The following steps will probably fail too ! So, please repeat my previous set of instructions, this time, using the correct package name in the "sudo apt purge ". You should be able to get to the stage where you can run - 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 dpkg -l | grep fpc dpkg -l | grep lazarus and get no response. Do not proceed to install anything until you can get to that stage.  Just to be clear, do not try and install FPC nor Lazarus until you get no response back to the two commands above. Use the command - 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 sudo apt purge Where the package_name is, one by one - lazarus-src-2.0 lazarus-project lazarus-ide-2.0 fpc-src fpc-laz I think you are going to have problems with that stage, so lets get it done before proceeding ! Davo ---------------------------------------------------------------------- Handoko · 2022-03-25 09:17 Synaptic Package Manager is a GUI tool that can help you remove broken package easily. And GDebi Package Installer can help you automatically install required missing packages. ---------------------------------------------------------------------- dbannon · 2022-03-25 11:40 Yeah, but neither are installed by default on Mint, its an Ubuntu clone.  And installing more packages right now sounds like a bit of a mistake until that apt database is thinking straight again. Davo ---------------------------------------------------------------------- Zoran · 2022-03-25 13:13 My advice is -- do not use deb packages -- use install script for fpc (called "one big file" in fpc download section), then install Lazarus from source. It's quite straightforward, you have control where fpc and lazarus will be installed (and you should put it under your user path). Also, unistalling is quite simple then -- it's just removing these folders. For details see (only now you use the latest fpc and lazarus versions, of course): https://forum.lazarus.freepascal.org/index.php/topic,35214 .msg246573.html#msg246573 ---------------------------------------------------------------------- Rama Can · 2022-03-26 16:26 I have run according to the command above 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 sudo apt purge < package_name > ---------------------------------------------------------------------- dbannon · 2022-03-26 23:19 OK, sounds like w are making progress.  By now I hope you are trying to understand the commands you are using ?  Its your system and it really should be your informed decision about what happens to it. Blindly following instructions form someone else, no matter how well intended is always risky. OK, Lets see of anything remains - 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 find /usr -name "lazarus-*" 2> /dev/null find /usr -name "fpc-*" 2> /dev/null If both those command come back cleanly, thats good, proceed. If you get a response from either command, you will have to decide if its an issue or not. Maybe you should remove it manually or, maybe you should not.  If its there incidentally, leave it alone, if it looks like its part of a previous install, maybe show us before acting ?  Remember that if you remove something you should not, really bad things will happen. On the other hand, if you leave it there and your next install fails, its easy to start again. So, if in doubt, leave it there ! Next, given the twisted history, maybe its a good idea to remove any old config files / directories ? This will find them, you know how to remove them by now. 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 find / -name ".fpc.cfg" 2> /dev/nullfind / -name "fpc.cfg" 2> /dev/null find / -name ".lazarus*" 2> /dev/null Only you can decide if you want to keep them, I suggest you dont ! All that done ? So, if you are happy with the above, maybe its time to start reinstalling !  You know how to do that too ! (but remember, use "apt" and use the "./" in front of the deb names. Or, as several people have mentioned, consider a source install, at least for Lazarus.  I personally would not use anything else. Its a touch harder but much more flexible and you will not find your self in the mixed up state you got into just now. Your call. People here will help you either way. Davo ---------------------------------------------------------------------- Rama Can · 2022-03-27 15:13 with that command, I found nothing,  and I feel that nothing bothers anymore Quoteram@ram-4G:~$ find /usr -name "lazarus-*" 2> /dev/null ram@ram-4G:~$ find /usr -name "fpc-*" 2> /dev/null ram@ram-4G:~$ find / -name ".fpc.cfg" 2> /dev/null ram@ram-4G:~$ find / -name "fpc.cfg" 2> /dev/null ram@ram-4G:~$ find / -name ".lazarus*" 2> /dev/null then I tried to install again with the command 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     cd     ls -l *.deb    // all good    sudo apt install ./fpc- laz_3.2.2_amd64.deb    // all good    sudo apt install ./fpc- src_3.2.2_amd64.deb    // all good    sudo apt install ./lazarus- project_2.2.0-0_amd64.deb    // all good i open lazarus, but there are parts missing, how to fix it? ---------------------------------------------------------------------- Rama Can · 2022-03-27 17:19 I think I'm quite happy with it so far, how do I fix the missing piece? ---------------------------------------------------------------------- dbannon · 2022-03-27 22:49 Quote from: Rama Can on March 27, 2022, 07:19:35 pmI think I'm quite happy with it so far, how do I fix the missing piece? You will have to tell us what piece is missing. Neither image you have posted appear to be missing anything. Davo ---------------------------------------------------------------------- dsiders · 2022-03-27 22:59 Quote from: dbannon on March 28, 2022, 12:49:18 amQuote from: Rama Can on March 27, 2022, 07:19:35 pmI think I'm quite happy with it so far, how do I fix the missing piece? You will have to tell us what piece is missing. Neither image you have posted appear to be missing anything. There is no object inspector. Use Window > Center a lot window and select Object Inspector from the menu. ---------------------------------------------------------------------- trev · 2022-03-27 23:02 And the missing Messages window should appear when you compile something. ---------------------------------------------------------------------- Rama Can · 2022-03-28 02:51 [Solved] thank you to all who have helped me patiently and sincerely, a very valuable experience to be able to talk to all of you, always healthy.