[Lazarus] Procedure List regression

[Russel Dirks]

The Procedure List dialog seems to have regressed slightly in the latest
version (1.7), under Windows. The first time you open it and type something
into the filter and press Enter, nothing happens, even if you got an exact
match from what you typed.  The reason seems to be that no line is selected
in the bottom listbox.  You have to use Down Arrow, or click with the mouse
to get a selected line, then you can press Enter.

 

After the first invocation, however, it seems to work normally, wrt the
Enter key.   

 

I also notice that the filter box is re-populated with text from the
previous invocation.   It would be nice if the text came up selected, so you
could just begin typing something and the previous entry would be deleted.

 

I am aware that some work has been done on this feature recently.  Just
providing some feedback.

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Lazarus Release 1.6

[silvioprog]

On Thu, Feb 18, 2016 at 12:16 PM, Mattias Gaertner <
nc-gaert...@netcologne.de> wrote:

> The Lazarus team is glad to announce the release of Lazarus 1.6.

[...]

Great job! \o/

(SF still "Looking for the latest version? Download
lazarus-1.4.4-fpc-2.6.4-win32.exe")

-- 
Silvio Clécio
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

[Lazarus] Lazarus Release 1.6

[Mattias Gaertner]

The Lazarus team is glad to announce the release of Lazarus 1.6.

This release was built with FPC 3.0.0.
The previous release Lazarus 1.4.4 was built with FPC 2.6.4.

Here is the list of changes for Lazarus and Free Pascal:
http://wiki.lazarus.freepascal.org/Lazarus_1.6.0_release_notes
http://wiki.lazarus.freepascal.org/User_Changes_3.0.0

The release is available for download on SourceForge:
http://sourceforge.net/projects/lazarus/files/

Choose your CPU, OS, distro and then the "Lazarus 1.6" directory.

Checksums for the SourceForge files:
http://www.lazarus-ide.org/index.php?page=checksums#1_6

Minimum requirements:

Windows:
  98, 2000, XP, Vista, 7, 8/8.1, 10, 32 or 64 bit.   
  Win98 and WinNT IDE needs FPC 2.6.4 and building with flag
-dWIN9XPLATFORM. 

FreeBSD/Linux:
  gtk 2.8 or qt4.5, 32 or 64bit.

Mac OS X:
  10.5 to 10.11, LCL only 32bit, non LCL apps can be 64bit.

The svn tag is
http://svn.freepascal.org/svn/lazarus/tags/lazarus_1_6

Here is the list of fixes for Lazarus 1.6:
http://wiki.freepascal.org/Lazarus_1.6_fixes_branch

For people who are blocked by SF, the Lazarus releases from SourceForge
are mirrored at: 
ftp://freepascal.dfmk.hu/pub/lazarus/releases/
and later at (after some time for synchronization)
http://michael-ep3.physik.uni-halle.de/Lazarus/releases/
and
http://mirrors.iwi.me/lazarus/

Mattias

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] TApplication.UpdateMainForm

[Ondrej Pokorny]

On 18.02.2016 11:53, Graeme Geldenhuys wrote:

On 2016-02-18 10:25, Ondrej Pokorny wrote:

So this is wanted and by design. It is also coming from Delphi.

>From what I remember (Delphi 7 and earlier), any TCustomXXX is used for
descendants and component writers. The "final" class without the
"custom" part in the name is simply a empty class, but with the
properties Published.

I know the Delphi form designer used TForm for descendants - I always
thought that to be wrong (from a design point of view). I understand why
Delphi did that though - to overcome the Delphi Form Designer
limitations, where it uses RTTI get read and set properties, and thus
needs published properties.

TApplication is not a component you can drop on a form though, so should
not be grouped with the same limitations as the Delphi Forms Designer.

My argument is exactly the same as why many components use TStrings as a
property parameter, instead of TStringList.


Your argument is valid for TStrings/TStringList, TCustomEdit/TEdit etc. 
but not for TCustomForm/TForm. This is a historical relict Lazarus has 
inherited from Delphi. Normal forms (that you put controls on and work 
with them normally) have to be inherited from TForm or you will be 
facing strange effects (like wrong PopupParent on ShowModal etc.). It's 
the same in Delphi.
There could be another design chosen but Delphi chose this one. You have 
to live with it.

As I said before, it's by design so your arguments are nil here.

Btw. Delphi 7 has no PopupParent property - it was introduced in Delphi 
2006 (maybe 2005 but who cares about it).


Ondrej

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] TApplication.UpdateMainForm

[Graeme Geldenhuys]

On 2016-02-18 10:25, Ondrej Pokorny wrote:
> So this is wanted and by design. It is also coming from Delphi.

>From what I remember (Delphi 7 and earlier), any TCustomXXX is used for
descendants and component writers. The "final" class without the
"custom" part in the name is simply a empty class, but with the
properties Published.

I know the Delphi form designer used TForm for descendants - I always
thought that to be wrong (from a design point of view). I understand why
Delphi did that though - to overcome the Delphi Form Designer
limitations, where it uses RTTI get read and set properties, and thus
needs published properties.

TApplication is not a component you can drop on a form though, so should
not be grouped with the same limitations as the Delphi Forms Designer.

My argument is exactly the same as why many components use TStrings as a
property parameter, instead of TStringList.


Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] TApplication.UpdateMainForm

[Ondrej Pokorny]

On 18.02.2016 10:40, Graeme Geldenhuys wrote:

On 2016-02-18 01:09, Fabio Luis Girardi wrote:

Because TForm publishes some properties that I want keep in protected
section.

That would have been my answer too.  I fully agree, classes or methods
should use the lowest possible class in the hierarchy, thus any
descendants are usable too.


There is a functionality difference between TCustomForm and TForm in the 
LCL.
See e.g. TCustomForm.GetRealPopupParent (uses Screen.ActiveForm) or 
TApplication.UpdateVisible (uses Screen.Forms).


So this is wanted and by design. It is also coming from Delphi. Every 
"normal" form that you use has to be a descendant of TForm if you like 
it or not.

Descendants of TCustomForm are special forms like hint windows etc.

Ondrej

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] TApplication.UpdateMainForm

[Mattias Gaertner]

On Wed, 17 Feb 2016 23:09:45 -0200
Fabio Luis Girardi  wrote:

> Em 17 de fev de 2016 18:41, "Mattias Gaertner" 
> escreveu:
> 
> > No.
> > Why can't you derive from TForm?
> 
> Because TForm publishes some properties that I want keep in protected
> section.

Why do you need a MainForm?

Mattias

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] TApplication.UpdateMainForm

[Graeme Geldenhuys]

On 2016-02-18 01:09, Fabio Luis Girardi wrote:
> Because TForm publishes some properties that I want keep in protected
> section.

That would have been my answer too.  I fully agree, classes or methods
should use the lowest possible class in the hierarchy, thus any
descendants are usable too.

Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] processing incoming mail

[Michael Van Canneyt]

On Thu, 18 Feb 2016, duilio foschi wrote:


we have a linux server with domain (say)

www.ourserver.com

A mail server of some type is installed.

The mail server uses the following mysql tables:

+--+
| Tables_in_mailserver |
+--+
| view_aliases |
| view_users   |
| virtual_aliases  |
| virtual_domains  |
| virtual_users|
+--+

Probably some of you will quickly recognize the sort of mailserver used
here (I dont remember its name).

By accessing these tables from MySQL I know how to create a new email
account and how to forward emails sent to each mail account.

Is there a way to programmatically intercept all incoming emails, process
them and eventually store them in a database ?


You should define a filter for your MTA. The filter is then a program you
write, and this program can do whatever it wants. It will need to report
back to the MTA. Usually some pre-defined exit codes are used for this.



If possible, I'd like to do that by Lazarus CGIs.


I don't think CGI is an option for such a system.

Michael.

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

[Lazarus] ANN: Glibc - Mega bug found

[Graeme Geldenhuys]

Hi everybody,

Better make sure your Linux distro patches Glibc.

  http://www.bbc.co.uk/news/technology-35592916


Regards,
  - Graeme -


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

[Lazarus] processing incoming mail

[duilio foschi]

we have a linux server with domain (say)

www.ourserver.com

A mail server of some type is installed.

The mail server uses the following mysql tables:

+--+
| Tables_in_mailserver |
+--+
| view_aliases |
| view_users   |
| virtual_aliases  |
| virtual_domains  |
| virtual_users|
+--+

Probably some of you will quickly recognize the sort of mailserver used
here (I dont remember its name).

By accessing these tables from MySQL I know how to create a new email
account and how to forward emails sent to each mail account.

Is there a way to programmatically intercept all incoming emails, process
them and eventually store them in a database ?

If possible, I'd like to do that by Lazarus CGIs.

What exactly I'd like to do is to check for some special tokens in the
incoming emails and store or forward them accordingly.

Please instruct me re where to start.

Thank you

Peppe
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Mode DelphiUnicode

[Michael Schnell]

Please see the forum thread "non Unicodode application" (and don't reply 
to a thread message wit ha new topic).


-Michael

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

[Lazarus] Mode DelphiUnicode

[Alfred]

Hello,

Would it be possible to add {$MODE DELPHIUNICODE} to the syntax mode 
choices of the Lazarus (1.7) parsing options ?


Thanks !


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus