Re: [Lazarus] Lazarus code editor improvement?

2019-11-16 Thread Bo Berglund via lazarus
On Sun, 3 Nov 2019 13:31:21 +0100, Joe via lazarus wrote: >> So indeed it is connected with VNC, but it also is connected with >> Lazarus' code editor window. It seems like this is the only affected >> window on the RPi, all others accept the composition key AltGr as part >> of entering a special

Re: [Lazarus] Why is setlength not allowed?

2019-11-16 Thread Michael Van Canneyt via lazarus
On Sat, 16 Nov 2019, Bo Berglund via lazarus wrote: I am trying to write a simple I2C interface program for Raspberry Pi but I am getting an error I don't understand... function TRaspiI2C.ReadI2CBytes(addr: integer; count: integer; buf: array of byte): integer; var i: integer; begin try

Re: [Lazarus] Find in files crashes Cinnamon

2019-11-16 Thread Juha Manninen via lazarus
Find in Files has some problem although it has not frozen the whole desktop earlier. There was a report from Jonas years ago: https://bugs.freepascal.org/view.php?id=24351 but it could not be reproduced and was finally resolved. There is also a more recent report: https://bugs.freepascal.org/view

Re: [Lazarus] Why is setlength not allowed?

2019-11-16 Thread Bo Berglund via lazarus
On Sat, 16 Nov 2019 09:20:28 +0100 (CET), Michael Van Canneyt via lazarus wrote: > > >On Sat, 16 Nov 2019, Bo Berglund via lazarus wrote: > >> I am trying to write a simple I2C interface program for Raspberry Pi >> but I am getting an error I don't understand... >> >> function TRaspiI2C.ReadI2CBy

Re: [Lazarus] Why is setlength not allowed?

2019-11-16 Thread Michael Van Canneyt via lazarus
On Sat, 16 Nov 2019, Bo Berglund via lazarus wrote: function InitI2cDevice(devpath: String; iDevAddr: Cint; var hInst: Integer): Integer; var iio : integer; begin try hInst := fpopen(devpath, O_RDWR); //Open the I2C bus in Read/Write mode iio := FpIOCtl(hInst, I2C

Re: [Lazarus] Why is setlength not allowed?

2019-11-16 Thread Bo Berglund via lazarus
On Sat, 16 Nov 2019 11:50:45 +0100 (CET), Michael Van Canneyt via lazarus wrote: >> I guess that the reason is that fpIoCtrl expects a pointer type >> variable so the typecast is done... Is there no alternative? > >The warning seems correct. I suspect Pointer(iDevAddr) is probably wrong. >Maybe