We are using TMS Web Core 2.5.4.0 and FNC UI Pack 5.6.0.0.
We have a main form which uses an off the shelf HTML template. The off the shelf HTML template has a div element to which our content forms are attached just as described in the TMS Web Core Developers Guide's Use off the shelf HTML Templates section.
In a content form, we have a TWebPanel component which wraps a TMSFNCKanbanBoard component. The TWebPanel component is associated with an HTML div element in the content form's HTML file. Though the FNC control is displayed, we encountered the following issues:
With the off the shelf HTML template used in the Web Core Developers Guide (creative-tim), the FNC control was not placed correctly. It was always placed too much to the right.
With another off the shelf HTML template (html5up-editorial), the FNC Kanban board items are not selectable and thus cannot be moved. If we move the div for the content form directly after the body tag in off the shelf HTML template (main form's HTML file), Kanban board item selection works.
Only FNC controls seem to be to have a problem with placement and selection, TWebXYZ-Controls which correspond to a HTML element work ok.
Do you have more details? I did a couple of tests with our demos (like TemplateUI) but I could not see an issue. If a problem persists, try to isolate and provide a sample source project with which we can reproduce the issue here.
I have setup two TMS Web Core projects one for each issue (off the shelf HTML template). The zip files are about 4 and 7 MB in size. How and to whom can I post them?
We found out that both issues are related to element positioning of controls.
As we understood, an FNC control is always positioned relatively to its container, e.g. a TWebPanel, and therefore, an FNC control's ElementPosition property is not published.
And yes, initially the FNC control is positioned relatively to its container.
But the FNC control's ElementPosition property is still there and absolute by default.
So if there are mouse clicks, the FNC's actual position is computed according to it's ElementPosition property which is absolute and mouse clicks will be outside the FNC control's (relative) rectangle in most cases.
It gets even worse, if you scroll down your web page and click an FNC control. It then moves up outside its container boundaries which is ok according to the ElementPosition property but not ok according to the relative position to its container.
Unfortunately, setting the container's and FNC's ElementPosition property programmatically to relative doesn't solve the problem, since the FNC control's vertical scroll bar and an FNC Kanban board's table and tree views are drawn elsewhere.
We would really appreciate to see these issues fixed in a beta version of a new FNC Core / FNC UI Pack version to proceed with our Web application development.
We now moved to TMS Web Core 2.6 beta and the newest versions of FNC Core (3.1.7.1) and FNC UI Pack (6.0.0.0).
We still found 6 issues with FNC controls:
Double-click on FNC Kanban board item does not always work.
If browser window's vertical scroll bar is not positioned top, the FNC Kanban board (or any other FNC control) moves up out of its parent,
if you click the free area next to the right-most column of the board,
if you resize the browser window,
if you want to drag a Kanban board item.
If you resize a memo which is located above the board, a web control below the memo is moved, but the FNC control is not.
If you collapse the sidebar, web controls are moved to the left, but the FNC control is not.