issue-#90 adding horizontal scroll bar to list boxes
Posted: Thu Dec 03, 2015 3:19 pm
This issue is for adding horizontal scroll bars to Lists and Selections.
For the issue see http://redmine.blackboxframework.org/issues/90.
The changes are mostly as proposed by Mathieu Westerweele in CPC 1.7 rc6 for SelectionBox.
The changes to CPC 1.7 rc6 are:
1. additional width of 5 pixels changed to Ports.point * 3 because then it is device independent.
2. the same changes are also applied to ListBox if not in drop-down mode.
For the changes see http://redmine.blackboxframework.org/pr ... 44888c2b98.
Plus: unused procedures ConvertFromUnicode and ConvertToUnicode removed.
This refers to another sub-entry in the CPC change list.
Remark:
When looking at the code I have seen that the list/selection box items are mapped by
Dialog.MapString. This was a big surprise for me.
Has anybody ever used this feature?
In my opinion, it is a mistake to map the contents of a control because it does not allow you to put arbitrary text in it.
The correct handling would be to call Dialog.MapString explicitly and only if needed before inserting with list.SetItem.
- Josef
For the issue see http://redmine.blackboxframework.org/issues/90.
The changes are mostly as proposed by Mathieu Westerweele in CPC 1.7 rc6 for SelectionBox.
The changes to CPC 1.7 rc6 are:
1. additional width of 5 pixels changed to Ports.point * 3 because then it is device independent.
2. the same changes are also applied to ListBox if not in drop-down mode.
For the changes see http://redmine.blackboxframework.org/pr ... 44888c2b98.
Plus: unused procedures ConvertFromUnicode and ConvertToUnicode removed.
This refers to another sub-entry in the CPC change list.
Remark:
When looking at the code I have seen that the list/selection box items are mapped by
Dialog.MapString. This was a big surprise for me.
Has anybody ever used this feature?
In my opinion, it is a mistake to map the contents of a control because it does not allow you to put arbitrary text in it.
The correct handling would be to call Dialog.MapString explicitly and only if needed before inserting with list.SetItem.
- Josef