Skip to content
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

Closed
corpsinhere opened this issue Jan 19, 2017 · 17 comments
Assignees
Labels
bug Confirmed bug in MaxTo.
Milestone

Comments

@corpsinhere
Copy link

No description provided.

@vegardlarsen vegardlarsen self-assigned this Jan 19, 2017
@vegardlarsen vegardlarsen added bug Confirmed bug in MaxTo. version-2015.11.1 labels Jan 19, 2017
@vegardlarsen
Copy link
Member

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.

@corpsinhere
Copy link
Author

corpsinhere commented Jan 21, 2017 via email

@vegardlarsen
Copy link
Member

No worries. I will look into this before the next release.

@corpsinhere
Copy link
Author

corpsinhere commented Feb 11, 2017

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)

@turkian
Copy link

turkian commented Mar 17, 2017

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/.

@rthill91
Copy link

rthill91 commented Apr 3, 2017

I'm seeing this same issue with MaxTo on Windows 10

@ghost
Copy link

ghost commented May 18, 2017

Same problem. Windows 10.

@ghost
Copy link

ghost commented Jun 8, 2017

Is MaxTo abandoned? Nobody seems to be correcting this countless bugs.

@vegardlarsen
Copy link
Member

@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.

@vegardlarsen
Copy link
Member

Did not mean to close the issue. :)

@artur-ag
Copy link

artur-ag commented Jul 3, 2017

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.
Tested on Windows 10, MaxTo 2015.11.1.0 and Unity 5.6.1f1.

EDIT: this also fixes the problem with ManicTime's interface.

@corpsinhere
Copy link
Author

corpsinhere commented Jul 3, 2017 via email

@tynril
Copy link

tynril commented May 18, 2018

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.

@vegardlarsen
Copy link
Member

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.

@rthill91
Copy link

No dice
MaxTo v2.0.0-alpha3
Unity v5.6.3p2

I'm still seeing the same behaviour

@vegardlarsen
Copy link
Member

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.

@vegardlarsen vegardlarsen added this to the 2.0.0-alpha.4 milestone May 28, 2018
@vegardlarsen
Copy link
Member

The fix I spoke of has been implemented, and will be in 2.0.0-alpha4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bug in MaxTo.
Projects
None yet
Development

No branches or pull requests

6 participants