It seems that flickering only appears when a new tab/doc is created...
Changing and closing tabs looks ok in my app.
Hope that helps

Hi

hologram, lionello, tobi do you see flickers on tab click/new tab or only on closing tab?

Flicker is still there.. my application looks like garbage using your workspace tabs.

Hello all.

there was fix in this area in 9.80, can you check how it looks now?

Here's why this is unbeliveably annoying. You decide you're going to have a nice tabbed workspace in your MDI app and min/max buttons available on child forms. Like Dreamweaver or Flash.

Then, you realize, that the workspace looks like crap when switching between child forms that aren't maxed. So, the only way to actually use the workspace AND have it look good, is not to have any options to resize forms... and simply a tabbed workspace.. which takes the shine off where your ideas were headed.

So, you explain to the company that you need this addressed, the flicker looks like a bug (it IS a bug/design flaw). You pay the company to stay subscribed to their updates, all in the hope it makes it to the next fix. Meantime, you short change the design of your app, becuase there's little other choice. Then, you post, politley, the problem, like my first post at the start of this thread. And the company (CodeJock) never replies. You know from the documentation that the forum is your only hope for getting the help you need. And they ignore you.

Net result, you learn that a great looking GUI tool is worthless without support to address important issues in some sort of time frame. We're not asking for a feature request, we're asking for something that NEEDS fixed to be fixed.

Why doesn't codejock include resizable child forms in a tabbed workspace in their examples, so you can see that it's going to look like crap ahead of time?

So, what keeps me going? Well, if they handle problems this way, they're leaving room for someone else to do better, inviting them even... and someone eventually will. Here you are, the 10th poster in this thread, and not a peep from CodeJock to address the issue except some crap work around that requires lowering YOUR OWN standards to fix the issue.. and insult to injury, the work around (oversizing forms) is even worse because now non-maximzed forms aren't user friendly. And that makes you wonder... what are you really dealing with here? Simple Incompetence? Software Crooks? Business Morons? and does it matter which it is?

Thanks CodeJock... nice way to treat your customers.