Forum Replies Created
-
Posts
-
Hi Serge,
I have modified your test application to demonstrate the problem but can't replicate it when I compiled it.
It seems that the memo fields are interacting with something else I have on the form or the mdi form. I'll continue to experiment with it to find out what is causing the problem.
I'll send back the test app when I find the offending component.
Regards
Colin
This is what the problem looks like when I navigate around the form – the problem only exists with memo fields, everything else works fine.
'Support' wrote:Hello Colin!
Everything is possible, but time is needed only.
For a skinning of wwDBLookupCombo a several special handlers should be made, but it's not possible at the moment.
I hope to find a time for this task later, but can't promise.
Hi, I realize that you have been very busy of late with the changes to alpha skins, but since it has been a year since I posted this request I though I might ask if there is any possibility of this item being kept on your “to do” list?
Many thanks
Colin
I've just been looking into replacing the woll2woll dblookupcombo with the TsDbLookupComboBox.
So far there are 2 problems which are stopping me from using it.
The first is that as far as I can tell, I can only nominate the one column to be displayed in the drop-down display. Ideally it would need to display multiple columns such as TMS's TAdvDbLookupComboBox or the twwDBLookupCombo. There are many circumstances where the knowledge of only one field is not enough to make the correct record selection.
The second problem is that at the moment the ListSource of TsDbLookupComboBox must be active for the DataField to be displayed. This is a show-stopper for me because it means that I would have to activate every lookup source on the form for the record to be displayed correctly. The resource overhead for that scenario is huge and not practical.
Would it be possible to add these changes to your dblookup combo? I for one would be very thankful if this were possible.
Regards
Colin
Ok thanks for looking in to it.
As I use the component throughout my application could you give me a bit more information regarding this problem as I'm trying to decide if I continue to use the component or not?
1) When you say it can't be fully supported at the moment do you think there will be a time when the component will be fully supported or is it unlikely that the component will ever work properly?
2) Could you give me some more details about why the component doesn't work at the moment? Is there something that Woll2woll need to do to modify their component, or is the problem on your side?
Regards
Colin
Not sure if I should add to this old thread, but I've found an exception to this rule that may be helpful to users of Billenium Effects 4. I'm using v4.4 beta 2 with DXE2 and found that I can not include a TsSkinProvider on the form if I want the transitions to work at all. I'm using the BE form transition effects rather sparingly so removing the TsSkinProvider from a small number of forms didn't seem to affect the performance of the skinning features, in my case, as far as I can tell.
Colin
