I have been tasked with re-writing a database app such that it uses a web interface.
Having had many years experience with xojo, I thought xojo web would be a good route to take as it would in theory allow me to port huge chunks of the application.
I have tried using controls such as WebTextField and added a got focused event. It doesn’t fire if the user uses the mouse (known bug apparently). It does however allegedly fire if the user presses tab. Well maybe, but certainly not every time.
So I’m currently left not knowing when a user has entered a text field. This effectively means I have no control over the user editing the data. I could always set the control to read only. Only that this appears to grey out the control. This is completely undesirable. This appears to be the same effect as setting the control’s enabled property to false. I’m sure there must be a difference?
Does anyone have suggestions on how I can prevent writing in the webTextfields / webTextAreas/ while not greying them out? The suggestion needs to cater for the fact if the user selects to edit data, all relevant controls are “enabled” for editing…
Other controls I have used include webcheck boxes, weblistboxes and webdatepickers…