I have a layout where the groups are locked, so that the end-user can't change what is in the groups, when they are customizing the layout. But, if I add a splitter between two locked groups, I cannot move the splitter to resize the groups. And, when I unlock those groups, I can resize them with the splitter. And, when I read the definition of the Locked property in the help, it doesn't mention that it also locks the size when not in customization mode in runtime, but only that the contents of the group cannot be modified in runtime.
Any help would be appreciated.
Hello,
I have reproduced the described behavior and forwarded this ticket to our developers for research. Meanwhile, I suggest that you try a workaround provided in the attached project (place a locked group into another group without borders).
Hello,
Thanks for the response. I did find that workaround after posting.
But, this is a layout that our end-users can also modify via customization, and will need to add the splitter themselves, since the splitters are not part of the initial layout. So, for the moment we will need to show our users somehow that if they want to use a splitter, they will need to put the locked group within another group, and to hide the border and caption of that new group. This is good for a short term solution, but in the long term it would be preferable that it wouldn't be needed, as we wouldn't have to show our users everytime they try to place a splitter in the layout and that it is not working. Especially, that most of them, their attention span can be very short and don't even bother reading our software's help, for instructions.
I hope that a fix can be provided for the next release.
Keep up the good work.
Hello,
I noticed that a fix for this wasn't in the latest version.
If a fix is available before the next version, I would like to have it.
Or, a little guidance as to which code that would need to look at, to fix the problem. I'm willing to a little bit of work to help get this issue fixed.
Thanks.
Hello,
You are right, the issue is not fixed yet. Our developers are still working on it. I assure you that they will do their best to resolve the problem as soon as they can.
We appreciate your patience.
Hello,
I also have an interest of this issue and workaround doesn't quite work for me.
How is going on here?
Thank you.
The issue is quite difficult and its fixing might have side effects. Thus, we need some additional time for tests. We appreciate your patience.