Jump to content

Recommended Posts

Posted

Hi Farshad

 

If you place a frame in a TUniTabControl and align it to client, it expands so much that it covers the tabs and borders of the parent TUniTabControl. This is happens in design mode and web mode. In runtime VCL mode it is displayed correctly inside the TUniTabControl.

 

Secondly, in design mode the frame does not inherit the (white) background of the TUniTabControl. It does in normal VCL apps. At runtime VCL/Web it works correctly.

 

Lastly there are still problems with labels on the frame. In Win32 mode the background of labels are gray. The frame itself inherits the white background from the TUniTabControl, but this is not handed down to the labels on the frame, which still think the background is grey. It works correctly in Web mode.

  • Administrators
Posted

Hi Farshad

 

If you place a frame in a TUniTabControl and align it to client, it expands so much that it covers the tabs and borders of the parent TUniTabControl. This is happens in design mode and web mode. In runtime VCL mode it is displayed correctly inside the TUniTabControl.

 

Secondly, in design mode the frame does not inherit the (white) background of the TUniTabControl. It does in normal VCL apps. At runtime VCL/Web it works correctly.

 

Lastly there are still problems with labels on the frame. In Win32 mode the background of labels are gray. The frame itself inherits the white background from the TUniTabControl, but this is not handed down to the labels on the frame, which still think the background is grey. It works correctly in Web mode.

 

I will test above issues and will include fix in next build.

  • Administrators
Posted

If you place a frame in a TUniTabControl and align it to client, it expands so much that it covers the tabs and borders of the parent TUniTabControl. This is happens in design mode and web mode. In runtime VCL mode it is displayed correctly inside the TUniTabControl.

 

BTW, why don't you use a TUniPageControl instead? You can have much more control on individual pages in TUniPageControl.

Posted

Well to make a long story short, the page is the same for each tab.

 

In my app, each tab indicates a particular record of a master table of which each client will typically only have access to one or a couple of records.

The plan is to use the tab selection to switch between the master record for each client. When the master record changes, a number of detail fields (UniDBText) which are displayed on the tab page changes. A few different pages are available, these are selected using a treeview like in your demo application.

 

Edit: I could probably put the Tab inside the frame instead of outside it, as a workaround.

  • Administrators
Posted

if you place a frame in a TUniTabControl and align it to client, it expands so much that it covers the tabs and borders of the parent TUniTabControl. This is happens in design mode and web mode. In runtime VCL mode it is displayed correctly inside the TUniTabControl.

 

fixed.

 

Secondly, in design mode the frame does not inherit the (white) background of the TUniTabControl. It does in normal VCL apps. At runtime VCL/Web it works correctly.

 

Design mode display may be different but at runtime it is OK.

 

Lastly there are still problems with labels on the frame. In Win32 mode the background of labels are gray. The frame itself inherits the white background from the TUniTabControl, but this is not handed down to the labels on the frame, which still think the background is grey. It works correctly in Web mode.

 

Is it only a design time issue?

Posted

Design mode display may be different but at runtime it is OK.

Correct. It is a very minor issue. As long as it is fine during runtime in VCL and Web mode, you can probably throw it pretty far down the backlog.

Is it only a design time issue?

No this is a rather visible runtime issue in VCL mode. Replicated in XE here:

 

post-28-0-80315000-1306351292_thumb.png

  • Administrators
Posted

Correct. It is a very minor issue. As long as it is fine during runtime in VCL and Web mode, you can probably throw it pretty far down the backlog.

 

No this is a rather visible runtime issue in VCL mode. Replicated in XE here:

 

Fixed.

×
×
  • Create New...