RadForm - FrameBorderStyle FixedSingle prevents activation?

5 posts, 1 answers
  1. Duane
    Duane avatar
    37 posts
    Member since:
    Sep 2010

    Posted 02 Dec 2010 Link to this post

    Hi Guys,

    Another question about the RadForm...

    We are using 2009.Q2 assemblies and have noticed that any forms that have a FrameBorderStyle set to FixedSingle that are behind another form will not accept a click in the client area to activate them. You can activate them by clicking the titlebar, but not the plain form area.

    There is no such issue with the Sizable frame border. Why is this?

    We have checked this in our main project, a simple one form project and also tweaking teh MDI example in teh example project. All behave the same. Is this a know issue and is it fixed in any versions later than 2009.Q2?

    Any advice appreciated.
    Regards,
    Duane
  2. Richard Slade
    Richard Slade avatar
    3000 posts
    Member since:
    May 2009

    Posted 03 Dec 2010 Link to this post

    Hi,

    I've tried this in a simple project using the latest Q3 2010 Version.
    I added 2 RadForms to the project.
    I set both to have a FormBorderStyle of Fixed Single
    I added a button to Form1 that would launch Form2

    I could launch form2 and swtich between the two forms by clicking on the client area of each form.
     
    Hope that helps. Advice is to upgrade to the latest version therefore.

    All the best
    Richard
  3. UI for WinForms is Visual Studio 2017 Ready
  4. Answer
    Duane
    Duane avatar
    37 posts
    Member since:
    Sep 2010

    Posted 06 Dec 2010 Link to this post

    Hi Richard,

    Thanks for your prompt reply. We have tried with the latest demo versions as well.  Sadly, as I have illuded to in many of the other threads I have raised about using these controls, We can't really look at upgrading to 2010 Q3, due to breaking changes. Our complete application has over 500 forms split over 5 sub applications. From the information on this site and replies from the Telerik staff I belive we could upgrade to the one of the latest 2009 control updates without upsetting too much of the code we have, but that is all.

    So.... using 2009 Q2 we have had to do a nasty workaround which is to set the FrameBorder to Sizable and then prevent the form resizing using the MaximumSize and MinimumSize propertie at runtime. This is not ideal as the cursor now indicates the form can be resized when actually it can't. Sadly we have to trade this off agaist not being able to activate other forms by clicking on them.

    Thanks anyway.
    Best regards,
    Duane.
  5. Richard Slade
    Richard Slade avatar
    3000 posts
    Member since:
    May 2009

    Posted 06 Dec 2010 Link to this post

    Glad you found a workaround for your current version, and apologies I couldn't help you find a more suitable solution
    Richard
  6. Duane
    Duane avatar
    37 posts
    Member since:
    Sep 2010

    Posted 07 Dec 2010 Link to this post

    Thanks for looking at it anyway. :)
Back to Top
UI for WinForms is Visual Studio 2017 Ready