TEditButton family and OnContextPopup lazarus / 31-LCL ---------------------------------------------------------------------- Sieben · 2020-09-07 19:09 Are there any special reasons why no descendant of TCustomEditButton - except for TEditButton itself - publishes OnContextPopup? ---------------------------------------------------------------------- Bart · 2020-09-07 21:04 Probably not. Can you make a patch and file a bugreport about that (and of course attach the patch file there)? Bart ---------------------------------------------------------------------- Sieben · 2020-09-08 08:03 Got the tutorials and will give it a try, thanks. ---------------------------------------------------------------------- Sieben · 2020-09-08 09:20 Sorry for coming back so soon, but from what I understand from this tutorial: https://wiki.freepascal.org/Creating_A_Patch I would have to additionally install Lazarus trunk first to create a working patch. As I am just getting familiar with Lazarus, it's settings, pathes etc, and not too familiar with Linux either, I'm not sure if I really want to do that at the moment. Would it be feasible if someone 'threw up' a current trunk EditBtn.pas here so I can create a patch with that one...? ---------------------------------------------------------------------- JuhaManninen · 2020-09-08 13:46 Quote from: Sieben on September 08, 2020, 11:20:17 amI would have to additionally install Lazarus trunk first to create a working patch. As I am just getting familiar with Lazarus, it's settings, pathes etc, and not too familiar with Linux either, I'm not sure if I really want to do that at the moment. Getting the trunk version is actually super-easy. Just make sure Subversion is installed, then in console : $ svn co https://svn.freepascal.org/svn/lazarus/trunk lazarus_trunk $ cd lazarus_trunk $ make $ ./lazarus & It also requires some development library packages from Ubuntu repository but you already have them from your earlier installation. You can have many versions of Lazarus in your machine the same way. No installation, just start them from their directory.  https://wiki.freepascal.org/Getting_Lazarus#Development_version_of_La zarus ---------------------------------------------------------------------- Sieben · 2020-09-08 15:28 Thanks, that sounds fairly easy indeed. Current dir in console should be my home directory then? ---------------------------------------------------------------------- JuhaManninen · 2020-09-08 16:09 Quote from: Sieben on September 08, 2020, 05:28:23 pmCurrent dir in console should be my home directory then? Yes, or any directory under it. You must have write access there. I myself keep all SW development projects under directory ~/SW. ---------------------------------------------------------------------- Sieben · 2020-09-08 19:58 Thanks again. Will do so tomorrow. ---------------------------------------------------------------------- Sieben · 2020-09-28 13:02 Finally filed: https://bugs.freepascal.org/view.php?id=37832 Sorry for delay, had to take a break for health reasons. This SVN stuff really works great, just one issue with installing 2nd copy of Lazarus: at first start you will be prompted about possible conflicts with configuration files, and best advice would be to start the 2nd copy with it's own configuration path like this: 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 ./lazarus -pcp=~/.lazarus_test but obviously this param expects double dashes (?) with it's short version as well: 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 ./lazarus --pcp=~/.lazarus_test ---------------------------------------------------------------------- valdir.marcos · 2020-09-29 09:44 Quote from: JuhaManninen on September 08, 2020, 03:46:59 pmQuote from: Sieben on September 08, 2020, 11:20:17 amI would have to additionally install Lazarus trunk first to create a working patch. As I am just getting familiar with Lazarus, it's settings, pathes etc, and not too familiar with Linux either, I'm not sure if I really want to do that at the moment. Getting the trunk version is actually super-easy. Just make sure Subversion is installed, then in console : $ svn co https://svn.freepascal.org/svn/lazarus/trunk lazarus_trunk $ cd lazarus_trunk $ make $ ./lazarus & It also requires some development library packages from Ubuntu repository but you already have them from your earlier installation. You can have many versions of Lazarus in your machine the same way. No installation, just start them from their directory. https://wiki.freepascal.org/Getting_Lazarus#Development_version_of_Laz arus1. How to get fpc trunk? 2. How to use fpc trunk to build lazarus trunk? ---------------------------------------------------------------------- Bart · 2020-09-29 10:55 Should be fixed in trunk by now. Bart ---------------------------------------------------------------------- Sieben · 2020-09-30 17:33 Thanks. Should this here topic be flagged as 'solved' then? ---------------------------------------------------------------------- JuhaManninen · 2020-09-30 18:02 Quote from: valdir.marcos on September 29, 2020, 11:44:39 am1. How to get fpc trunk? 2. How to use fpc trunk to build lazarus trunk? FPC trunk is a little more complicated than Lazarus trunk. I guess FpcUpDeluxe is the easiest way to get it. Using the development trunk version of both FPC and Lazarus increases the chance for temporary hiccups. I personally like to develop Lazarus with a released version of FPC. ---------------------------------------------------------------------- Bart · 2020-09-30 19:14 Quote from: JuhaManninen on September 30, 2020, 08:02:14 pmFPC trunk is a little more complicated than Lazarus trunk. I guess FpcUpDeluxe is the easiest way to get it. Assuming you have a svn client and you have fpc 3.2.0 installed it is quite easy. Code: [Select]svn co path/to/fpctrunksources cd  path/to/fpctrunksources make all make install //installs the compiler in c:\pp if you are in Windows fpcmkcfg -o .\fpc.cfg You can supply e.g. OPT="-gl"  to the make command, so that you have a fpctrunk with debug info (slower, but quite nice to have). Bart