Bug when place a ContainerControl inside tabpanel?

OS: Linux.
Tested using Xojo 2015R3 and 2016R4.1

I need someone to test this simple project. Is this a bug? or am I doing wrong? This behaviour is also occured in windows, but I can’t reproduce it.

https://www.dropbox.com/s/voqjls467v2c5bz/test.xojo_binary_project?dl=0

Looks like it’s a Linux thing

Yes, you’re right. tested on windows again and it works. On Linux, you need to resized the windows to make it works.

Oh? If a window-resize fixes it that can sometimes mean that it’s a re-drawing issue.
Does self.invalidate or self.refresh in the button’s action event help at all?

No, It doesn’t work

It only works with self.maximize. self.minimize doesn’t work.

It’s really strange. This code also works

Self.Width = self.Width + 10

but not this one

Self.Width = self.Width + 10
Self.Width = self.Width - 10
  • self in the code above is Window1.

Oh well, time to stop using Linux as a desktop, right?
:wink:

I don’t think so. This bug is related to Xojo not linux. So, we can’t blame linux here :D.

You should report it so it gets proper attention.

I see the same on 16r4.1, Linux Mint 18.

I’ve created a bug report - feedback://showreport?report_id=46611

Is this bug solved in the next release? Several of my private apps depend on this issue. I can’t continue to work on the apps at this moment.

When a bug is fixed, it appears in Feedback. That is not the case.

Then probably we still see the issue in the next release. Thank you Michel.

the case appeared as “implemented” when it is planned for a future release
this does not mean the next release, but a future one.
when it is done, it becomes as “verified&fixed”

[quote=317042:@Jean-Yves Pochez]the case appeared as “implemented” when it is planned for a future release
this does not mean the next release, but a future one.
when it is done, it becomes as “verified&fixed”[/quote]
Thank you for the detail explanation. I’m really new to Xojo feedback system.

Solved this issue by myself.

it would be nice to explain briefly how you did solve it, so that further users can solve it too ?

Unfortunately, this issue can’t be solved by using xojo code. You need to listen to a GTK signal and correct the position.

Well, maybe Xojo would be interested in what the underlying problem is and how to fix it

Sometimes I wish there was a Dislike button.