TListFilerEdit compile error lazarus / 31-LCL ---------------------------------------------------------------------- Marq01 · 2016-07-10 13:25 Hi, I was trying to make a new component with a TLabel as parent. At the first compilation I get this error: 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 listfilteredit.pas(44,15) Error: There is no method in an ancestor class to be overridden: "TListFilterEdit.MoveNext(Boolean="FALSE");" and more. First I don't see a relation with Tlabel. Second nothing will compile anay more... A cannot roll back to a working Lazarus system anymore. Anyone a suggestion? Arnoud ---------------------------------------------------------------------- Cyrax · 2016-07-10 13:50 Show us a full source code. ---------------------------------------------------------------------- wp · 2016-07-10 13:59 Did you already install the new component into the IDE? NEVER don't do that in this early stage. There will be lots of bugs, and each of them will kill the new component - and the IDE because after installation your component is part of the IDE. ALWAYS write a test program which creates and tests your program at runtime, you don't even have to put the new component into a package for this. Only if you don't find any more bugs this way add the component to a package and install it. In the rare case that still something is wrong and crashes the IDE you can revert to the previous version by deleting lazarus.exe and renaming lazarus.old.exe to lazarus.exe. Once you got back to a working lazarus at first unstall the new component and repeat testing. As for the compilation error, I cannot say much because of too little information. ---------------------------------------------------------------------- Marq01 · 2016-07-10 14:04 @Cyrax: After a clean up and build Lazarus 1.6 worked again. For code: I just followed the wizard yet. No coding whatsoever. http://wiki.freepascal.org/How_To_Write_Lazarus_Component At the point that the wizard should rebuild Lazarus everything went wrong. Second time also. Look at this: 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 Berichten, Warnings: 3Warning: other unit files search path (aka unit path) of "SPRpackage 0.0" contains "D:\Biacore\Programmas\SPR-Simulation", which belongs to package "TSuperLabelPakket"Warning: Duplicate file "rtfdata.inc" in "LazRichEdit 0.1.5", path="D:\Biacore\Programmas\BiaM ethodwriter\BiamethodW\Components\lzRichEdit\interfaces\gtk2\rtfdata.i nc"Warning: Duplicate file "rtfdata.inc" in "richmemopackage 1.0", pat h="D:\Biacore\Programmas\BiaMethodwriter\BiamethodW\Components\TRichMe mo\rtfdata.inc"Compile package LazRichEdit 0.1.5: Exit code 1, Errors: 1gtk2wsrichbox.pas(41,29) Fatal: Cannot find Gtk2Proc used by Gtk2WSRichBox. Enable flag "Use Unit" of unit Gtk2Proc in package LCL.Compile package EditorMacroScript 0.0: Succes!Compile package jcfidelazarus 2.0: AbortedCompile package LazDebuggerGdbmi 0.1: Succes!Compile package leakview 1.0: Succes!Compile package MemDSLaz 1.2.1: AbortedCompile package printers4lazide 0.0: AbortedCompile package ProjTemplates 1.0: AbortedCompile package TurboPowerIPro 1.0: AbortedCompile package richmemopackage 1.0: Aborted  As a beginner I have no clue. For now  I have to focus on my project and will deal with a new component one other time. Are there any books or websites you can recommend? @WP Your point is well taken. Learned today the hard way. Quote you don't even have to put the new component into a package for this Ah, where can a find to do that? I thought a component should be in component pallet before use. Kind regards Arnoud ---------------------------------------------------------------------- wp · 2016-07-10 14:19 Quote from: Marq01 on July 10, 2016, 04:04:21 pmAs a beginner...Beginning with component writing is the VERY hard way, and probably will leave you disappointed. Write a few standard applications first before you think of writing your own components. Quote from: Marq01 on July 10, 2016, 04:04:21 pmQuote you don't even have to put the new component into a package for thisAh, where can a find to do that? I thought a component should be in component pallet before use. Let me use the TCustomControl1 of the tutorial that you refer to as an example. And we assume that this control is implemented in unit customcontrol1. Write a little test program with just an empty form and this OnCreate event handler of the form: 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 procedure TForm1.FormCreate(Sender: TObject);begin  newcontrol := TCustomControl1.Create(self);  newcontrol.Parent := self;  newcontrol.Left := 8;  enwcontrol.top := 8;  // ... and set other properties hereend; In this example you must declare a private member newcontrol: TCustomControl1 of the form. And you must add "customcontrol1" to the interface uses clause. 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 uses  ..., customcomponent1, ... type  TForm1 = class(TForm)    ....  private    newcomponent: TCustomComponent1;    ...  end; Either store this demo in the same folder which contains the customcontrol1 unit, or add the path to this unit to your project options. Run and debug. Only after this is done without any errors you can continue with the tutorial. The tutorial covers only the mechanics of creating a package and adding the new component to this package. The hard work, however, is to write the new component! ---------------------------------------------------------------------- Marq01 · 2016-07-10 18:58 To be fair I have some experience with Delphi from ten years ago. But, I agree, designing a component is hard work as learning all the ins and outs of lazarus. Therefore, I appreciate all the good advice and the support of you guys. Got the first steps working. Thanks. Arnoud