Hello

Every QT user please test package
components/1_spartaBasic/dtx_spartabasic.lpk from the free-sparta branch, together with AnchorDocking.
It implements a docked form editor.
It works for other testers with QT bindings but not for me. I cannot add or select components.
Maybe depends on QT version. I have Manjaro with KDE 5 Plasma. QT4 is 4.8.7-2. I will test with other Linux distros soon.

Juha

Well for starters, on first start, I get an oversized Object inspector. Meaning: The object inspector (not docked) is more (maybe 100 to 200 more) than 1680 pixel in width (1680 = width of my screen)

This is without the above package added, just added anchordocking Win32 / Vista / 32 bit

What I did:
- checkout branch
- copy Qt4Pas5.dll / 5.2.5.0 into folder
- copy my (win32, not QT / no anchordocking) lazarus.exe into folder
- point lazarus.cfg to new empty primary config path
- start IDE
- set fpc (2.6.4), gdb, ...
- recompile
- launch

And the OI window was that massivly wide.
I have a desktop spanning 2 screens, left screen at -1680 to -1, right at 0 to 1679.

After closing IDE, from anchordocking.xml
<Item2 Name="ObjectInspectorDlg" Type="Control">
<Bounds Left="-181" Top="212" Width="1910" Height="550"> <WorkArea>
<Rect Right="1680" Bottom="1050"/>
</WorkArea>
</Bounds>
</Item2>

Strange though on next start the OI is still that wide, but its left is adjusted to the screen (at x=0)

Get a compile error with fpc 2.6.4
strange fcl-stl is in the source folder of fpc 2.6.4, but it is not build, there are no ppu for it.
So testing with an fpc from the 3.0.1 branch.

I can add, select and work with components.

Couple of thinks
1) might be qt in general. I can see items that are behind a panel. I can not see them on win32.
2) While resizing the form there is a (partial) fuchsia colored border (instead of the dotted grey)
Sometimes several pixel wide, sometimes just one. Sometimes all edges, sometimes just some, sometimes only parts of some edges.
3) Mouse does not change to resize, when over he border (grab-dots) of a selected component. But when click and move, resize will work. (strange, works (shows cursor) after restart...)
4) Moving items, sometimes leaves grabber dots (ghosts). They clear when the mouse button is released
(this is an effect of "reduced designer painting => so not related)
5) When the form is bigger than the space, a scrollbar appears (for the designer). It works, except it has a far too big scrollrange. The slider can only be moved in the top fraction of the bar, (which is enough to scroll the whole form)
Clicking on the empty space of the bar, goes ONE pixel only.
6) The form shows grabber dots at the top and left. They can not be used. Actually all form grabber dots do not work. To resize a form one has to grab the border of the form (at a pos without grabber dot). But still no top/left...
Well the grabber dots of the form work in a freshly started IDE. They stop at some point.
7) A form with AutoScroll, shows no scrollbars (for the form) even if needed
8) Also on restart, I sometimes get a ghost form1 (a none docked, only border painted, none usable floating form1). Seems to disappear when I select the designer tab

9) With multiple SourceEdit win: The first time the designer is shown in a newly opened 2ndary win, the form is empty, but after switching to the designer in the first win, and back, it will be ok

Martin Frb wrote

9) With multiple SourceEdit win: The first time the designer is shown in a newly opened 2ndary win, the form is empty, but after switching to the designer in the first win, and back, it will be ok

Closing the unit in one window, and then selecting designer of that unit in another win, gives an exception "object reference is nil)

Not yet able to reproduce though...

Problem also, if MOVING editro between windows. After that the designer is no longer accesible for that editor

Martin Frb wrote

So testing with an fpc from the 3.0.1 branch.

For info version of QtCore4.dll
4.8.5.0

Does it work with win32, gtk2 ?

zeljko

---------- Forwarded message ----------

I have X11.
Wayland is still alpha and not usable for normal work, according to what I have read.
KDE5 Plasma desktop on the other hand is very usable now. I have noticed only few small bugs, yet many thigs are improved from KDE4 times.

Juha

---------- Forwarded message ----------