RTI_MIGRATE_V9_TO_V10 (OpenInsight 64-bit)
At 24 JAN 2022 11:20:39PM Barry Stevens wrote:
Bob,
In OI9, the practice of some developers' design is to use the visual of a combobox’s button to show that the ‘dropdown’ button will bring up a selection action, say, a popup.
To this effect the comboBoox is resized so the dropdown ‘list’ area does not show.
In OI10 there is no need to ‘resize’ as this dropdown list action is determined by the default property setting “Behaviour→AutoDropDown”.
When this form is run through the OI9 conversion, This is set to 1 for all comboboxes .
This now requires going through all the forms and changing the ‘AutoDropDown’ to 0 where there is not a dropdown required (as explained above).
Would it be possible in the conversion to tell by the size of the combo if there is a dropdown list at design time, and if there was not, have the value of AutoDropDown’ set to 0.
Thank you for your consideration.
At 28 JAN 2022 04:20AM Andrew McAuley wrote:
Obvs I'm not Rev but that is SO developer specific that I'd imagine it'd make more sense for you to run a post conversion utility to make the change you want yourself. Read the window rec, check the drop down, set the property flag accordingly?
ps:www.sprezzatura.com]The Sprezzatura Group[/url] The Sprezzatura Blog World leaders in all things RevSoft
</QUOTE> —- === At 28 JAN 2022 07:12PM Barry Stevens wrote: === <QUOTE> <QUOTE>Obvs I'm not Rev but that is SO developer specific that I'd imagine it'd make more sense for you to run a post conversion utility to make the change you want yourself. Read the window rec, check the drop down, set the property flag accordingly? ps:www.sprezzatura.com]The Sprezzatura Group[/url]
World leaders in all things RevSoft
Thank you.
I will see if I can work out how to do that along with other issues.
</QUOTE>
At 28 JAN 2022 09:23PM Carl Pates wrote:
Hi Barry,
I would not be keen on relying on the height of a control to determine that this is what a developer wants - to me it leaves too much room for error.
The best person to be a judge of this is you, and as Andrew says this is something than can be fairly simple to implement.
The property you are interested in is a PS style bit:
equ PSS_COMBO_MANUALDROPDOWN$ to 0x00000002 ; * // AUTODROPDOWN property (inverse)But this is an Inverse bit, i.e. for an AUTODROPDOWN of False the PSS_COMBO_MANUALDROPDOWN$ bit needs to be set!
Ergo, for the combos you want to update make sure this PS style bit is set.
Regards,
At 29 JAN 2022 01:35AM Barry Stevens wrote:
Hi Barry,
I would not be keen on relying on the height of a control to determine that this is what a developer wants - to me it leaves too much room for error.
The best person to be a judge of this is you, and as Andrew says this is something than can be fairly simple to implement.
The property you are interested in is a PS style bit:
equ PSS_COMBO_MANUALDROPDOWN$ to 0x00000002 ; * // AUTODROPDOWN property (inverse)But this is an Inverse bit, i.e. for an AUTODROPDOWN of False the PSS_COMBO_MANUALDROPDOWN$ bit needs to be set!
Ergo, for the combos you want to update make sure this PS style bit is set.
Regards,
Carl,
Agreed.
Thanks for the heads-up.
bw: Forgotten my binary stuff, am I ANDing or ORing.?
plus:
How do I check if not already set so I dont unset?
At 31 JAN 2022 07:41PM Carl Pates wrote:
Barry
Check if a bit is set you use BitAnd
Ensure a bit is set you use BitOr
Remove a bit you use BitNot and BitAnd
Regards
At 31 JAN 2022 11:27PM Barry Stevens wrote:
Barry
Check if a bit is set you use BitAnd
Ensure a bit is set you use BitOr
Remove a bit you use BitNot and BitAnd
Regards
Awesome , thanks