Re: [Lazarus] Form in DLL

This is almost exactly the way I wrote plugin architecture for my apps. The difference is that the dll function call (which opens a form) is blocked within Application.Initialize and Application.Terminate, so the dll function (and the form) lifetime is only along the executed function. The only cur

Re: [Lazarus] Form in DLL

2012/4/30 Michael Fuchs : > Hello, > > in http://bugs.freepascal.org/view.php?id=1866 is described, that forms > in dlls are not working at this moment. I have coded a dll which opens a > form and it works. But I am not sure if there are some hidden problems > or side-effects. I have once also exp

Re: [Lazarus] Strip debug info

2012/4/30 Richard Mace : > This is interesting, I'd had never actually thought of a work flow like > this. So, would you have 2x different projects? 1 with as dubug and the 2nd > as release, or is there a better way of doing it? There are build modes. There is a page in the project options dialog

[Lazarus] Form in DLL

Hello, in http://bugs.freepascal.org/view.php?id=1866 is described, that forms in dlls are not working at this moment. I have coded a dll which opens a form and it works. But I am not sure if there are some hidden problems or side-effects. Before I implement this in a real application, I want to r

Re: [Lazarus] Return of Frame3D issue

On 30/04/12 23:15, Frank Church wrote: In upgrading to Lazarus 1.1 and issue I first came across in this thread has returned. I think I decided not to use the controls in 0.9.31 but I want to consider them again in Lazarus 1.1, http://lists.lazarus.freepascal.org/pipermail/lazarus/2011-Augus

[Lazarus] Return of Frame3D issue

In upgrading to Lazarus 1.1 and issue I first came across in this thread has returned. I think I decided not to use the controls in 0.9.31 but I want to consider them again in Lazarus 1.1, http://lists.lazarus.freepascal.org/pipermail/lazarus/2011-August/065582.html . There is also a mantis issue

Re: [Lazarus] Strip debug info

> Well, the problem is the size of the exe file. ;-) > > When I am working on a project I usually want to generate debug > > information for debugging. > > But when I give the generated file to someone else I surely do not need > > this information in the exe file anymore. > > So why should I be f

Re: [Lazarus] Strip debug info

On Monday, April 30, 2012 09:37 Michael Schnell wrote: > On 04/29/2012 12:09 PM, Martin wrote: >> Then you have an outdated debug info file, > The "release" build could just delete this file (provided it's there > where a corresponding "debug" build would create it). > -Michael Please do

[Lazarus] Overloading with generic type as parmeter causes compiler error.

Hi All! I am working on a generic type library and ran into a problem at compile time. type generic TMyType = class * * * function IndexOf( Item : T ) : Integer; overload; functionIndexOf( aName : String) : Integer; overload; // generics1.pas Error: Function is already declared Public\

Re: [Lazarus] Removing read-only files in FileUtil.DeleteDirectory ?

Bart schrieb: > I would change the declaration to: > function DeleteDirectory(const DirectoryName: string; > OnlyChilds: boolean; const RemoveReadOnlyFiles: Boolean = False): boolean; Yes, I think this needs to be changed/added . And what about system-hidden files? Are they already deleted

Re: [Lazarus] build modes - I have an idea

On 30/04/12 17:45, Juha Manninen wrote: On Mon, Apr 30, 2012 at 12:13 PM, patspiper > wrote: True, but they are very flexible: - They override the setting you need, and leave the other settings as per the default build mode - No need to change a common

Re: [Lazarus] build modes - I have an idea

On Mon, Apr 30, 2012 at 12:13 PM, patspiper wrote: > True, but they are very flexible: > - They override the setting you need, and leave the other settings as per > the default build mode > - No need to change a common setting in several places (paths, target > filename, checks, etc...) > - You c

Re: [Lazarus] Object inspector hints ?

On 30 April 2012 09:23, Mattias Gaertner wrote: > On Mon, 30 Apr 2012 10:03:41 +0200 (CEST) > Michael Van Canneyt wrote: > > > > > Hi, > > > > The lazarus code editor shows tooltip hints about identifiers; It gets > those > > from the sources or even fpdoc. > > > > Is there any reason why the ob

[Lazarus] RE : RE : Removing read-only files in FileUtil.DeleteDirectory ?

> > How to find out what went wrong? > Maybe add parameter 'ExceptionOnError:boolean=false' and if > true then raise an exception with the file name. > Good idea. I just kept it along the lines of the existing DeleteDirectory that just failed without raising a exception. Ludo -- ___

Re: [Lazarus] RE : Removing read-only files in FileUtil.DeleteDirectory ?

On Mon, 30 Apr 2012 14:16:22 +0200 "Ludo Brands" wrote: > > Regarding issue #21855 > > http://bugs.freepascal.org/view.php?id=21855 > > > > I am planning to reject the patch but I would like to have other > > opinions, too. > > I'm in favor of patch with current definition (no default parame

[Lazarus] RE : Removing read-only files in FileUtil.DeleteDirectory ?

> Regarding issue #21855 > http://bugs.freepascal.org/view.php?id=21855 > > I am planning to reject the patch but I would like to have other > opinions, too. I'm in favor of patch with current definition (no default parameters as suggested by Bart) and with following ammendment: if Remov

Re: [Lazarus] Removing read-only files in FileUtil.DeleteDirectory ?

On 30/4/12 11:45, Bart wrote: On 4/29/12, Juha Manninen wrote: I would change the declaration to: function DeleteDirectory(const DirectoryName: string; OnlyChilds: boolean; const RemoveReadOnlyFiles: Boolean = False): boolean; If the suggestion is adopted it needs to be function De

Re: [Lazarus] Removing read-only files in FileUtil.DeleteDirectory ?

On 4/29/12, Juha Manninen wrote: Removing files in windows can fail also. The flag RemoveReadOnlyFiles actually means try to also remove read-only files (just like DeleteDirectory actually tries to delete a directory). As long as the function returns False if removing of a file/dir fails it shoul

Re: [Lazarus] Object inspector hints ?

On 30/4/12 11:54, Hans-Peter Diettrich wrote: Howard Page-Clark schrieb: What's the use of such additional information in OI? You can let the OI create the event handler for you, no need to bother with parameters here. For people who use a stable release all the time, set up according to

Re: [Lazarus] Inconsistent results from MessageDlg()

On 4/29/12, patspiper wrote: >> Someone with a recent Delphi (as in> D3) tested this for me. > Delphi XE? Yes, executable run under XP. Bart -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailma

Re: [Lazarus] Object inspector hints ?

Howard Page-Clark schrieb: Right click on OI: enable Show hints There is also the (optional) OI information box which displays limited documentation. However, it is often very limited. e.g. "TControl.OnClick Event Handler for mouse click" which hardly aids a programmer looking for more inf

Re: [Lazarus] Object inspector hints ?

On Mon, 30 Apr 2012 09:50:30 +0100 Howard Page-Clark wrote: > On 30/4/12 9:23, Mattias Gaertner wrote: > > On Mon, 30 Apr 2012 10:03:41 +0200 (CEST) > > Michael Van Canneyt wrote: > > > >> > >> Hi, > >> > >> The lazarus code editor shows tooltip hints about identifiers; It gets > >> those > >>

Re: [Lazarus] build modes - I have an idea

On 30/04/12 02:02, Juha Manninen wrote: The GUI should indeed be more intuitive. It should indicate the build more setting is "above" all other settings, affecting them all. Build mode modifier/override is a good idea, too, but requires (maybe difficult) code changes. True, but they are very

Re: [Lazarus] Object inspector hints ?

On 30/4/12 9:23, Mattias Gaertner wrote: On Mon, 30 Apr 2012 10:03:41 +0200 (CEST) Michael Van Canneyt wrote: Hi, The lazarus code editor shows tooltip hints about identifiers; It gets those from the sources or even fpdoc. Is there any reason why the object inspector would not be able to of

Re: [Lazarus] Object inspector hints ?

On Mon, 30 Apr 2012, Mattias Gaertner wrote: On Mon, 30 Apr 2012 10:03:41 +0200 (CEST) Michael Van Canneyt wrote: Hi, The lazarus code editor shows tooltip hints about identifiers; It gets those from the sources or even fpdoc. Is there any reason why the object inspector would not be abl

Re: [Lazarus] Object inspector hints ?

On Mon, 30 Apr 2012 10:03:41 +0200 (CEST) Michael Van Canneyt wrote: > > Hi, > > The lazarus code editor shows tooltip hints about identifiers; It gets those > from the sources or even fpdoc. > > Is there any reason why the object inspector would not be able to offer the > same hints ? > Prop

[Lazarus] Object inspector hints ?

Hi, The lazarus code editor shows tooltip hints about identifiers; It gets those from the sources or even fpdoc. Is there any reason why the object inspector would not be able to offer the same hints ? Properties and events are also just identifiers after all. Michael. -- ___

Re: [Lazarus] Strip debug info

On 04/30/2012 05:49 AM, Alexander Klenin wrote: When I tried to persuade my students to switch to Lazarus from Delphi, I've got many complaints about Lazarus being too slow. About a third of these complaints were fixed by either excluding Lazarus directory from AV's monitoring list, or turning -X

Re: [Lazarus] Strip debug info

On 04/29/2012 12:09 PM, Martin wrote: Then you have an outdated debug info file, The "release" build could just delete this file (provided it's there where a corresponding "debug" build would create it). -Michael -- ___ Lazarus mailing list La