In a large project I found out that after on resizing of the form, some
components get properly resized but don't receive an Invalidate call. I
guess, it's caused by the test in lcl/include/control.inc
if not ((csLoading in ComponentState) or (Self is TWinControl)) then
InvalidateControl(IsC
On 04/05/2020 11:05, Bo Berglund via lazarus wrote:
On Mon, 4 May 2020 10:25:42 +0100, Tony Whyman via lazarus
wrote:
As to the filename issue: the xml file location is determined from the
Vendor Name and application name and relative to $HOME/.config - is that
really a problem?
First off:
I
El 4/5/20 a les 11:25, Tony Whyman via lazarus ha escrit:
TRegistry is a very useful way of saving dynamic configuration data
(e.g. mainform co-ordinates) in order to preserve them from one program
session to another - and to do so in a cross-platform manner. IMHO. it
would be a significant lo
On Mon, 4 May 2020 10:25:42 +0100, Tony Whyman via lazarus
wrote:
>As to the filename issue: the xml file location is determined from the
>Vendor Name and application name and relative to $HOME/.config - is that
>really a problem?
First off:
I would NOT use the Registry ever for my new applica
I often use TRegistry for cross-platform configuration data and you
should be able to use it and avoid having to maintain different Linux
and Windows versions.
Under Linux, you are using TXMLRegistry and this saves registry data in
an application specific XML file. There can be both a common X
On Mon, 4 May 2020, Bart via lazarus wrote:
On Mon, May 4, 2020 at 12:41 AM Bo Berglund via lazarus
wrote:
structure:
HKLM\SOFTWARE\Companyname\Applicationname\Server\(named values)
HKLM\SOFTWARE\Companyname\Applicationname\Configuration\(named values)
The *nix way is to use .conf files
Firstly, the question is about TRegistry and not TRegIniFile. On a *nix
platform TRegistry is implemented using TXMLRegistry and not TRegIniFile.
You should only have a single instance of a TXMLRegistry in any one
program no matter how many times you create a TRegistry object - they
all point
Is there a problem on FC32?
Mattias
At least on my system, unless
https://bugs.freepascal.org/view.php?id=36976
is applied, Lazarus is not usable. This definitely applied to trunk, and
my limited testing suggested older versions could be affected also.
Colin
--
_
On Thu, 30 Apr 2020 09:08:58 -0300
silvioprog via lazarus wrote:
> On Thu, Apr 30, 2020 at 5:01 AM C Western via lazarus <
> lazarus@lists.lazarus-ide.org> wrote:
>
> > On 25/04/2020 11:27, C Western via lazarus wrote:
> > > I have recently upgraded to Fedora 32 beta ...
>
>
> [offtopic]:
On Mon, May 4, 2020 at 12:41 AM Bo Berglund via lazarus
wrote:
> structure:
> HKLM\SOFTWARE\Companyname\Applicationname\Server\(named values)
> HKLM\SOFTWARE\Companyname\Applicationname\Configuration\(named values)
The *nix way is to use .conf files (basically ini-files) for that.
IIRC you have
Hi Bo,
looking into xregreg.inc:
procedure TRegistry.SysRegCreate;
var s : string;
begin
s:=includetrailingpathdelimiter(GetAppConfigDir(GlobalXMLFile));
ForceDirectories(s);
FSysData:=TXMLRegistryInstance.GetXMLRegistry(s+XFileName);
TXmlRegistry(FSysData).AutoFlush:=False;
end;
It's s
11 matches
Mail list logo
