fpGUI Toolkit v1.0 release for FPC 2.6.2

[BigChimp]

There are still no FPC tools to compile a *.rc text file into a *.res binary file. Windows has it, but Linux, FreeBSD etc doesn't.

Yes they do; windres from the mingw binutils:
http://wiki.lazarus.freepascal.org/Lazarus_Resources#Checking_you_have_windres

[Graeme]

And if you chose to willingly cut off features form the fpGUI for the general public by not including "toolbox" for DPI "fix", the blame is yours alone. Deal with it.

By the way, I did my own tests with LCL. Attached is a form designed at 96 dpi using Lazarus LCL-GTK2. I then started X11 set to 140dpi and ran the test app - look what happened.  Oops! Text gets clipped and all. I guess your "all holy and perfect" LCL once again doesn't work the same on all platforms. LCL's high DPI might work automatically under Windows (thanks to Microsoft's efforts), but it sure doesn't under Linux or FreeBSD.

So LCL is in the same boat as fpGUI.

[Graeme]

Yes they do; windres from the mingw binutils:

I don't have it on any of my four Linux systems, nor on my FreeBSD system. Why doesn't FPC ship the binary with the FPC releases? fpGUI can't rely on something the developers will in all likelihood not have on their systems. All compiling of projects will then fail - that to me is worse.

[BigChimp]

Agreed.

I opened a bug against the .deb packages. The maintainer had some reason (I forgot already) to not include it in the REQUIRED list or even the RECOMMENDED list.

I then gave up.

[Blaazen]

Graeme, I did the test (RadioButtons in autosized GroupBox) and it works well (Qt and GTK2). Looking at the first screenshot - it seems that GroupBox.AutoSize=False (because there is a gap below the third RadioButton). Such test makes no sense.

[Fred vS]

it seems that GroupBox.AutoSize=False (because there is a gap below the third RadioButton). Such test makes no sense.

Ooops, indeed, i just see it now.

So the conclusion is : the advice of a Professor is better than that of a Doctor.

( well seen Blaazen  )

[itmitica]

@ Itmitica

In my book, what you are right now is either naive or oblivious.

Maybe, but in my book, when i try something new, and if i find something bad i ask :

Hello. I just try your new release, i find something strange when i change the DPI resolution, is that normal ?

And i wait for the solution.

If no answer, maybe i gonna say the release is not perfect.

I never gonna begin posting something like you :

Your release is shit, Lazarus people, do not use it...

But, sure, we do not read the same books.

You said  that developers have to educate their clients.

I say, please, start with educating yourself even.....

I can see why you took up CS.
Stand-up comedy just isn't your thing.
Just make sure you don't mix the two of them too often.
It may lead you to entertaining people with the software you produce.

--
Mitică

[BigChimp]

Could we keep this thread polite please?

[itmitica]

Could we keep this thread polite please?

Yeah, you see, four-letter-word shit didn't came out of my keyboard.
Making solid tests and talking smack are not the same, so yeah, I'm gonna take offence.

--
Mitică

[Graeme]

Looking at the first screenshot - it seems that GroupBox.AutoSize=False (because there is a gap below the third RadioButton). Such test makes no sense.

I know its possible, by changing properties, implementing OnResize event handlers, implementing ScaleDPI(), using advanced anchoring options etc... My point was [to the annoying person] that simply dropping components on the form and then running it at various DPI values will not result in correct scaling. In that regard, fpGUI is no worse than LCL. Some other work [however easy or difficult] is required to get correct scaling.

[Fred vS]

@ Itmitica. Excuse my keyboard, he does not know what he did.

You speak cash and i like that. Your tests are profitable for everybody, many thanks. But the way you present them is rough.

If you pay cash, accept that the change is cash as well.
But i agree i have to educate myself too...
Hope we gonna take something positive from that battle.

[Graeme]

Ooops, indeed, i just see it now.

You also missed the point of my comparison. See my previous message.

In any case, to fix my LCL example, I would have to apply AutoSize = True to the GroupBox, all RadioButtons, Label, Edit, Button, and somehow calculate the new size of the Form itself (not sure if TForm has an AutoSize property). So "with some effort" scaling can work, so fpGUI is no worse than LCL in that regard.

[Fred vS]

So "with some effort" scaling can work

For myself, even if scaling works perfectly, i never gonna use autosize. I do not trust any more in autosize (always bad surprises). I have developped since years my own functions autosizer/positionner, so i can control everything by myself with code that i know.

[Blestan]

@Graeme

Hi do you plan do impelement a platform independant message loop or to make possible to use  multiple mesage loops in fpGui?

this will be a very interesting feature

best regards and bravo for the good work!

[itmitica]

In any case, to fix my LCL example, I would have to apply AutoSize = True to the GroupBox, all RadioButtons, Label, Edit, Button, and somehow calculate the new size of the Form itself (not sure if TForm has an AutoSize property). So "with some effort" scaling can work, so fpGUI is no worse than LCL in that regard.

You don't need to calculate the new size of the form. The feature you're looking for are anchor points.
I'm blown away by the fact that you don't know what I consider to be basic interface construction in LCL.
Big big question mark for someone trying to build an alternative widgetset to LCL.

--
Mitică