Re: [Lazarus] WMEnterSizeMove Messages not firing

On 10.10.2015 15:36, Aradeonas wrote: Now I get a kind message from Székely Balázs that show a temporary way. Great! Thanks Balázs for the code and also thanks for sharing! I added the workaround to the bug report: http://bugs.freepascal.org/view.php?id=23302 Ondrej --

Re: [Lazarus] lazcontrols filters

TextHint could be visibile even when edit is focused (but still empty of course). This is how many edit controls work nowadays, e.g address edit in FireFox -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org

Re: [Lazarus] WMEnterSizeMove Messages not firing

Its a temp way and it should work the easy way but for now its good to go. Regards, Ara -- http://www.fastmail.com - Access all of your messages and folders wherever you are -- ___ Lazarus mailing list

Re: [Lazarus] lazcontrols filters

On 10.10.2015 17:52, Krzysztof wrote: TextHint could be visibile even when edit is focused (but still empty of course). This is how many edit controls work nowadays, e.g address edit in FireFox This is exactly what I was thinking. The rekonq browser has the same. It is even able to put a

[Lazarus] Built Lazarus on RPi2, warning on every project build

I have successfully compiled and installed fpc and lazarus from trunk sources retrieved by svn on a Raspberry Pi2 unit. Versions are 3.1.1 and 1.5 respectively I can run Lazarus in the RPi2 and simple programs that I have tested work as expected. But nevertheless on every single compile there are

Re: [Lazarus] lazcontrols filters

On Sat, Oct 10, 2015 at 7:38 PM, Ondrej Pokorny wrote: > This is exactly what I was thinking. The rekonq browser has the same. It is > even able to put a button in front of the text in the edit and start the > text after the edit + the hint text is centered. I admit that I

Re: [Lazarus] Built Lazarus on RPi2, warning on every project build

On 10/10/2015 03:13 PM, Bo Berglund wrote: I have successfully compiled and installed fpc and lazarus from trunk sources retrieved by svn on a Raspberry Pi2 unit. Versions are 3.1.1 and 1.5 respectively I can run Lazarus in the RPi2 and simple programs that I have tested work as expected. But

[Lazarus] Lazarus eats comment characters using Swedish keyboard

A problem surfaced just a moment ago... I was writing code in Lazarus ver 1.5 running on a Raspberry Pi2 with Raspbian Jessie. I wanted to comment out a number of lines so I hit the key combination to produce the { } pair. But nothing was printed in the Lazarus editor. If I switched to the text

Re: [Lazarus] Accessing GPIO on RaspberryPi2 from Lazarus/FPC

On Thu, 08 Oct 2015 23:30:10 +0200, Bo Berglund wrote: >I have found a description of a unit implementing an interface to the >gpio driver in the Free Pascal documentation. It is here:

Re: [Lazarus] Codetools question

On 10.10.2015 12:35, Michael Van Canneyt wrote: Hi, Mainly for Mattias, I suppose: The SetString routine in the system unit has become a compiler procedure in 3.0: {$ifdef FPC_HAS_CPSTRING} Procedure fpc_setstring_ansistr_pansichar(out S : RawByteString; Buf : PAnsiChar; Len : SizeInt;

Re: [Lazarus] Codetools question

On Sat, 10 Oct 2015, Ondrej Pokorny wrote: On 10.10.2015 12:43, Michael Van Canneyt wrote: On Sat, 10 Oct 2015, Ondrej Pokorny wrote: On 10.10.2015 12:35, Michael Van Canneyt wrote: Hi, Mainly for Mattias, I suppose: The SetString routine in the system unit has become a compiler

Re: [Lazarus] Codetools question

Am 10.10.2015 12:47 schrieb "Ondrej Pokorny" : > > I think it is save to assume that Lazarus was compiled with the same FPC version that is also used for the sources in editor. Therefore you can use the same compiler directive: Not necessarily. As a compiler developer I often

Re: [Lazarus] Codetools question

On 10.10.2015 13:00, Michael Van Canneyt wrote: This is definitely not so :-( I compile lazarus with 2.6.4, but work with compiler set to 3.0 or even jvm. That is how I bumped into the problem to begin with... :-) CodeTools know what compiler constants are defined in the target tool. You

[Lazarus] Codetools question

Hi, Mainly for Mattias, I suppose: The SetString routine in the system unit has become a compiler procedure in 3.0: {$ifdef FPC_HAS_CPSTRING} Procedure fpc_setstring_ansistr_pansichar(out S : RawByteString; Buf : PAnsiChar; Len : SizeInt; cp: TSystemCodePage); rtlproc; compilerproc; {$else}

Re: [Lazarus] Codetools question

On Sat, 10 Oct 2015, Ondrej Pokorny wrote: On 10.10.2015 12:35, Michael Van Canneyt wrote: Hi, Mainly for Mattias, I suppose: The SetString routine in the system unit has become a compiler procedure in 3.0: {$ifdef FPC_HAS_CPSTRING} Procedure fpc_setstring_ansistr_pansichar(out S :

Re: [Lazarus] Codetools question

On 10.10.2015 12:43, Michael Van Canneyt wrote: On Sat, 10 Oct 2015, Ondrej Pokorny wrote: On 10.10.2015 12:35, Michael Van Canneyt wrote: Hi, Mainly for Mattias, I suppose: The SetString routine in the system unit has become a compiler procedure in 3.0: {$ifdef FPC_HAS_CPSTRING}

Re: [Lazarus] Accessing GPIO on RaspberryPi2 from Lazarus/FPC

I agree, this is a really, really nice find. Not only because of the rpi code, their xml parser implementation is the most easiest to debug I have ever seen, not the usual pointer chaos seen in all the other implementations. Hopefully there are even more gems hidden in this library. Michael

Re: [Lazarus] Accessing GPIO on RaspberryPi2 from Lazarus/FPC

On Sat, 10 Oct 2015, Michael Ring wrote: I agree, this is a really, really nice find. Not only because of the rpi code, their xml parser implementation is the most easiest to debug I have ever seen, not the usual pointer chaos seen in all the other implementations. The difference will be

Re: [Lazarus] WMEnterSizeMove Messages not firing

Now I get a kind message from Székely Balázs that show a temporary way. > Hi Ara, I saw your conversation with Ondrej about catching the > WMEnterSizeMove and WMExitSizeMove message. I did respond on the > mailing list, unfortunately my mails still get filtered out(this was > also confirmed by