I'll ask internally. However, this might be a scenario in which a fix can have significant side effects in many existing applications, as we need to change the method logic (which is likely incorrect, I know). Is adding a check for "Showing" a potential workaround?
Off topic: XE5: TPageControl and tabs on a frame - I have weird experiences with editing names and captions of the tabs - the IDE UI appears to be losing focus on the field in the property editor. Anyone else seen that?
Marco Cantù If you look into the CanFocus method you see that it loops through the controls up to the point where it finds the ParentForm but it does NOT check if that form is Enabled/Visible. If you include that the function result should be correct.
While playing around with different scenarios I realized that the exception thrown in SetFocus at least for Windows 8 is a lie. You can infact focus an invisible control (if you make it visible again it contains focus). Which is funny because FMX behaves like that. Maybe that code is over a decade old and a relict from ancient windows times.
Also putting workaround code inside the VCL to make the form designer in the IDE work might not been the smartest idea ever made.
Oh please yes. We're bitten by this too at times, annoying!
ReplyDeleteI'll ask internally. However, this might be a scenario in which a fix can have significant side effects in many existing applications, as we need to change the method logic (which is likely incorrect, I know). Is adding a check for "Showing" a potential workaround?
ReplyDelete"by design" :P
ReplyDeleteThat would be a nice fix.
Off topic: XE5: TPageControl and tabs on a frame - I have weird experiences with editing names and captions of the tabs - the IDE UI appears to be losing focus on the field in the property editor. Anyone else seen that?
Marco Cantù If you look into the CanFocus method you see that it loops through the controls up to the point where it finds the ParentForm but it does NOT check if that form is Enabled/Visible. If you include that the function result should be correct.
ReplyDeleteWhile playing around with different scenarios I realized that the exception thrown in SetFocus at least for Windows 8 is a lie. You can infact focus an invisible control (if you make it visible again it contains focus). Which is funny because FMX behaves like that. Maybe that code is over a decade old and a relict from ancient windows times.
Also putting workaround code inside the VCL to make the form designer in the IDE work might not been the smartest idea ever made.