J
jquerijero
Guest
By the way, OE supports pre-defining the bindingsource temp-table and fields. Just assign it later with a datasource with the same structure. This should allow you to take advantage of the UI designer when defining your individual control binding. [quote user="Kai Siegele"] Hallo Mike, thanks for your tip, but I would prefer a solution with a strong seperation between the data object and it’s properties and calculations on the one hand and the user interface with the representation and input on the other hand. Such a solution is easy to maintain and extend when a formular must be corrected or the user input changes from a TextBox to a slider. For connecting controls of the UI and data object, so that data object knows when the value in control has changed and control knows when property of data object has changed I need in C# only a few lines of code f.e. tbRating1.DataBindings.Add("Text", bindingSource, "Rating1", false, DataSourceUpdateMode.OnPropertyChanged); tbRating2.DataBindings.Add("Text", bindingSource, "Rating2", false, DataSourceUpdateMode.OnPropertyChanged); ... btnSave.DataBindings.Add("Enabled", bindingSource, "IsValid", false, DataSourceUpdateMode.OnPropertyChanged); That’s great, isn’t it? And I am still searching for a similar solution in ABL. Do you have any idea? Kind regards Kai Siegele [/quote]
Continue reading...
Continue reading...