Author Topic: Maximizing window make part of the interface unavailable  (Read 4308 times)

Gaxil

  • Newbie
  • *
  • Thank You
  • -Given: 2
  • -Receive: 0
  • Posts: 7
    • View Profile
Maximizing window make part of the interface unavailable
« on: February 16, 2015, 04:10:14 PM »
I have a strange problem that occurs only when unity runs stand alone and never when I'm in the editor. When I start my program, every buttons/sliders are available and are working fine, but if I increase the size of the window (either maximizing it or dragging it) every buttons/sliders that are now in the extended part of the window are not responding (the debug info told me that I'm on the UI root even when above one of them.). If I start with a larger window, no problem, I can shrink it, everything is fine and I can increase its size again without any problem. It really looks like the available area for the UI is defined at the start of the program and is never updated again.

Any help would be welcome :) ... Thanks in advance.


ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: Maximizing window make part of the interface unavailable
« Reply #1 on: February 17, 2015, 09:30:52 PM »
Wasn't it a reported Unity regression bug in Unity 4.6.2? It works properly in 4.5.5.

Gaxil

  • Newbie
  • *
  • Thank You
  • -Given: 2
  • -Receive: 0
  • Posts: 7
    • View Profile
Re: Maximizing window make part of the interface unavailable
« Reply #2 on: February 18, 2015, 01:24:43 AM »
It is happening in Unity 5 RC2 for sure and since many versions of unity5, but I'm not sure about the 4.x version as I've moved my project to V5 since some weeks/months now.

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: Maximizing window make part of the interface unavailable
« Reply #3 on: February 18, 2015, 05:04:23 PM »
Yeah, just another regression issue on Unity's end. They broke it in 4.6 and it propagated to 5.0