Log in to start a topic

Extended part of dropdown not populated with columns

Posted by: piotrolech on 27 September 2017, 9:05 pm EST

  • piotrolech

    • Post Options:
    • Link
      Copy

    Posted 27 September 2017, 9:05 pm EST

    Something went wrong in one of recent updates of C1Combo (My current version is 4.0.20162.174).

    When Dropdownwidth property is set wider then combo itself, then while runtime, opened dropdown displays columns only to width of combo - the extended part remains blank.

    To correct it some steps are needed in design time:

    enter designer, change Split.SplitSizeMode from Scalable to other value (Exact), then save changes, enter designer again and change SplitSizeMode back to Scalable. After that, dropdown displays correctly.

    Unfortunately, that applies not only to newly created controls, but also to the existing ones.

    It’s serious bug - I have used quit a number of C1Combo in my application and now lot of them look awful.

    Customers are disguisted. It’s impossible to correct them all manually, but I can’t find a way to do it in code. Comparing PropBag of ‘bad’ combo before and after correction, I’ve found, that ClientRect of the Split object has changed.

    Please, do something asap or provide a workaround

    Regards,

    Peter

  • nilayvishwkarma

    Posted 27 September 2017, 9:05 pm EST

    Hi Peter,

    Please find the attached sample. I am not able to replicate your issue in it. Could you modify and resend me the sample so that I can report it to the developer.

    ~nilay

  • nilayvishwkarma

    Posted 27 September 2017, 9:05 pm EST

  • piotrolech

    Posted 27 September 2017, 9:05 pm EST

    Hi Nilay,

    sorry for delayed answer, but it was really hard to reproduce the problem. It seems, that in most cases, putting new combo on a form and setting it up from scratch doesn’t cause the problems (however in my application I was able to get it a couple of times). So this is how I prepared a sample: there are 2 forms, on the first one I put a combo, prepared it in designer and then I copied PropBag to resx file and an InitializeComponents section from one of my application forms, where I encountered a problem. The second form is a copy of the first one, but I did the following: I entered a combo designer, on Split tab I changed SpliSizeMode from Scalable to Exact - that was enough to get the dropdown part look correctly. Then I set SplitSizeMode back to Scalable and it still looks good. It seems that changing SplitSizeMode helps. Unfortunately it works only in design mode, I tried to change it in code in runtime, but it has no effect. I have a lot of ‘old’ combos im my application, so I wouldn’t like to correct them all manually. Please try to correct the problem or provide a workaround.

    Regards,

    Peter

    2016/10/C1ComboBug.zip

  • nilayvishwkarma

    Posted 27 September 2017, 9:05 pm EST

    Peter,

    [i]> Unfortunately it works only in design mode, I tried

    to change it in code in runtime, but it has no effect[/i]

    I am not sure if this is possible. Can you try this making sure you are following the exact steps as form2.

    I would have to expand and check the propbag.

    ~nilay

  • piotrolech

    Posted 27 September 2017, 9:05 pm EST

    Nilay,

    First of all tell me if you can see the difference how the combos look like on form1 and form2?

    Can you try this making sure you are following the exact steps as form2. I would have to expand and check the propbag.

    I’m not sure what exactly you want me to do…

    Do you want me to prepare form3 as exact copy of form1, than try to change the SplitSizeMode in code to see if it helps (instead of doing it in designer)?

    Or something else?

    Peter

  • nilayvishwkarma

    Posted 27 September 2017, 9:05 pm EST

    Peter,

    Sorry for the confusion. I have reproduced the issue and reported this to the devs.

    Internal ID: (214125)

    ~nilay

  • jxburns

    Posted 27 September 2017, 9:05 pm EST

    Was there any update on this?

    I have very similar problems following an update made in last 3-4 months and I’m now trying to make changes to an older application.

    In my case setting columnwidth to -1 (i.e. to show all visible columns), as it always has been, results in a transparent box with nothing in it.

    Setting to 0 shows the items but only column 0.

    Setting to something like 400 shows the pop-up but totally blank.

    In my case changing the SplitSizeMode, as suggested by Peter, has no effect.

    This is using C1Combo 4.0.20163.212. All other C1Combo in the form work perfectly - the subtle difference being they all have only one visible column unlike the one with the problem.

    Thanks - John

  • nilayvishwkarma

    Posted 27 September 2017, 9:05 pm EST

    Hi John,

    This issue is fixed in an internal build. The fix would be provided in v3.5 release.

    Build: 4.0.20163.215

    ~nilay

  • jxburns

    Posted 27 September 2017, 9:05 pm EST

    OK thanks. Any timescale for release (even pre-release) as stopping an existing application working but with new updates that fixed another problem?

    John

  • nilayvishwkarma

    Posted 27 September 2017, 9:05 pm EST

    Hi John,

    Find the latest winforms internal build at:

    (4.0)

    ftp://supportftp.componentone.com/supportftp/public/nilay/C1WinForms.4_4.0.20163.217.zip

    (2.0)

    ftp://supportftp.componentone.com/supportftp/public/nilay/C1WinForms.2_2.0.20163.217.zip

    Please be advised that these builds are not fit for release yet but you can use them for internal fixes/testings. I won’t advise using this for production.

    Steps to install these builds:

    1. Close all instances of Visual Studio
    2. Create backup for “C:\Program Files (x86)\ComponentOne”
    3. Copy the Apps folder from the zip file to “C:\Program Files (x86)\ComponentOne\Apps”
    4. Copy all other folders/files directly from zip file into “C:\Program Files (x86)\ComponentOne\WinForms Edition”, so that the content are replaced.

    ~nilay

  • jxburns

    Posted 27 September 2017, 9:05 pm EST

    Was this ever released into production? I am now using v4.0.20171.248 and problem still occurs. The pre-release version from 3+ months ago works fine.

    Thanks - John

  • nilayvishwkarma

    Posted 27 September 2017, 9:05 pm EST

    Hi,

    I am unable to reproduce this. With the build 248, this issue is found fixed. Find the attached sample to verify this.

    ~nilay

    2017/04/C1ComboBug.zip

  • jxburns

    Posted 27 September 2017, 9:05 pm EST

    Your sample worked fine.

    However have found the problem. Setting DropDownWidth to -1 no longer works properly (in my system) as it has done for several years. In the past this would tell the control to display the dropdown as the sum of the individual column widths. Now it literally does what it says and displays in a dropdown of zero width. Changing to match the sum of the individual column widths solves the problem.

    When I try this with your sample it still works OK so there must be something else, in combination with dropdownwidth, that is stopping the dropdown displaying correctly in my system. It may be related to a field that is generated using unboundcolumnfetch but whilst I can replicate the problem by changing back to -1 I cannot yet find out what other property is causing this to fail.

    I note in 4.0.20163.225 change log that reference is made to this problem and that fixed following my earlier report. Can you ask the developers if what they did would have had the effect I mention above in the logic of dropdownwidth and setting to -1? There has been no change to the code so problem must lay in the control itself.

    Thanks - John

  • nilayvishwkarma

    Posted 27 September 2017, 9:05 pm EST

    Hi,

    Even with an isolated sample, DropDownWidth is working properly. Can you provide me with some steps to reproduce this or perhaps a sample? Without reproducing this issue, it won’t be possible to fix this. Sorry.

    ~nilay

    2017/04/C1ComboDropDownIssue.zip

  • jxburns

    Posted 27 September 2017, 9:05 pm EST

    I’m not sure how I can send you a sample from an application that has been running for best part of 15 years without a problem until end of last year when only thing changed was to update the control and recompile.

    As I said could you not ask the developer rather than trying to play around with a sample yourself? They may be able to confirm that dropdownwidth option of -1 no longer works because of the changes they have made elsewhere - if the only solution is to no longer use -1 then so be it. As the only item to change is that control then has to be related to it and should not assume it is my system.

    Thanks - John

  • nilayvishwkarma

    Posted 27 September 2017, 9:05 pm EST

    Hi John,

    I have asked the devs as per your request. I would let you know if there are any updates from their end.

    ~nilay

  • jxburns

    Posted 27 September 2017, 9:05 pm EST

    Nilay

    Thanks for the update and appreciate your efforts.

    However by process of literally testing each property change I have been able to create something as per attached sample which hopefully may give some clues.

    “Bad” exhibits the problem and was literally copied from my application, changed to AddItem mode (columns cleared) and then loaded with 4 items (could not be bothered to sort out a datasource).

    “Good” was created from scratch (from toolbox) and I worked through each property until I could get problem to occur but very weird.

    As you will see “Good” works fine with DropDownWidth=-1. But now change the FONT property to something else - I chose “Tahoma 10” which I use in all my applications as people tend to like a bigger font but any will do.

    You should see it no longer drops down. Obviously just using a non-default font should not cause this problem.

    John

    2017/04/TestCombo1.zip

  • nilayvishwkarma

    Posted 27 September 2017, 9:05 pm EST

    Hi,

    This would definitely help.

    Thanks,

    ~nilay

  • e12cs.ruchir.agarwal

    Posted 14 November 2017, 10:12 am EST

    Hi John,

    With the build 282, this issues is fixed. Dropdown opend when

    
cmbo.DropDownWidth = -1
cmbo.ReadOnly = False

    ~nilay

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels

  • © 2023 MESCIUS USA, Inc. All Rights Reserved.  ·  1.800.858.2739

    All product and company names herein may be trademarks of their respective owners.