[Lazarus] Form Resizing

[Bo Berglund]

On Sun, 6 Mar 2016 23:47:19 +0100, Giuliano Colla
<giuliano.colla at fastwebnet.it> wrote:

>Il 06/03/2016 18:27, Bo Berglund ha scritto:
>[...]
>> I have no idea what you mean by this statement...
>> What is LXDE and how do I test Lazarus for LXDE?

>A general hint: whenever you don't know what an acronym means (such al 
>LXDE = Lightweight X11 Desktop Environment, which btw is most likely the 
>desktop you're using), or how to take advantage of a popular control 
>version program like svn, just type its name in a Google search, and 
>you'll get all the information, tutorials and discussions you might 
>wish, in order to understand what is it, get acquainted with it, use it 
>and be aware of its features and bugs.

OK, I grant you that I formulated this rather poorly...

But nevertheless, I do not know how to test Lazarus on an RPi3 (or
RPi2) with the Raspbian distribution using anything but what the
distribution provides. So therefore I failed to get the connection
between Lazarus and LXDE....

I have located the release document for Raspbian Jessie here:
https://www.raspberrypi.org/blog/raspbian-jessie-is-here/
A little bit down they write the following:

<quote>the appearance of Raspbian is now based on version 3 of GTK+,
the user interface toolkit used for the LXDE desktop environment. The
older version 2 of GTK+ is slowly being replaced with version 3
</quote>

If this means that Raspbian is using LXDE is beyond me but it seems
like it is using gtk3 by this wording.

When I try to find a gtk3 setting inside Lazarus I only do so in the
dialog Tools/Configure_BuildLazarus, where it is contained in a
dropdown box labelled "LCL widget type" and named "gtk3 (alpha)".

There seems to be no way to build an *application* with gtk3 without
rebuilding the whole Lazarus environment first, is this the case?

PS:
I only started writing in this thread because I also fond the same
behaviour as the original poster did and it seemed like that report
was shunned as being bogus.
So I wanted to chip in with my observations to help *the developers*
to nail down and fix the problem, but now I find I am being flamed for
doing so so I will stop this.
I did not originate the thread.
DS

-- 
Bo Berglund
Developer in Sweden