-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unity 5.5 editor window does not repaint on window resize while MaxTo is running. #165
Comments
This is on Windows 10? It could be that MaxTo is doing something strange here; but it could also be Unity's fault. I am logging this for something that needs closer examination. |
Oh man I am really sorry - this is for Win 7. I hope I did not send you on a
wild goose chase.
…On Thu, Jan 19, 2017 at 12:18 AM, Vegard Andreas Larsen < ***@***.***> wrote:
This is on Windows 10? It could be that MaxTo is doing something strange
here; but it could also be Unity's fault. I am logging this for something
that needs closer examination.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#165 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AYC4q30VJ3rzfdxVc3YBCA1nsPzhA3NUks5rTxxvgaJpZM4LnlDO>
.
|
No worries. I will look into this before the next release. |
Looks like MaxTo is also interfering with repainting the Jing preview window. The window turns black if moved -problem goes away when MaxTo is closed. (to be clear this is on win7) |
I have the same problem with ManicTime tracker on Windows 10. Only the border will be drawn after moving the window. A free version is available if you need it for testing : http://www.manictime.com/. |
I'm seeing this same issue with MaxTo on Windows 10 |
Same problem. Windows 10. |
Is MaxTo abandoned? Nobody seems to be correcting this countless bugs. |
@Balimund We have not abandoned it, and there is a bug fix in the works. We are currently waiting for our installer software to support installing .NET Framework 4.7, which was released last month. I do not think we will have this bug fixed though, as it appears to be more difficult to track down. |
Did not mean to close the issue. :) |
This happens when MaxTo's windows transparency option is activated. If you disable it, Unity's interface won't stop drawing after you move it. This should serve as a workaround, and maybe help tracking down the bug. EDIT: this also fixes the problem with ManicTime's interface. |
Works! Thanks for tracking this down :D.
|
I'm also experiencing this bug (with Windows 10, MaxTo 2017.7.0.0, and Unity 2017.3.1f1), but the workaround suggested by @artur-ag worked. |
Can anyone please try this again with the preview releases (specifically 2.0.0-alpha.3)? See #220 on how to test it. We've changed quite a bit about how MaxTo subclasses other windows, and it is likely this problem will be solved. |
No dice I'm still seeing the same behaviour |
You should now be able to go into Settings, Compatibility and press Check for updates to download a new compatibility shim that will prevent this issue for Unity. The shim is a bit heavy handed, and disables all subclassing for Unity for now, which means you'll loose functionality such as drag-to-region for the main Unity window. I am also adding the capability of targetting just the window transparency option with a compatibility shim, which is what is causing the issue with Unity in the first place. This will have to wait until the next alpha release. |
The fix I spoke of has been implemented, and will be in 2.0.0-alpha4. |
No description provided.
The text was updated successfully, but these errors were encountered: