herculanojs

Hello, I managed to solve all the problems with TMS.

Hello, I managed to solve all the problems with TMS. Tell me which point has difficulty, that I can help you.

could you tell if the 1508 would work?

version 1.70.0.1486

I am getting an error while compiling. procedure TUniQZ.Connect; begin JSCallGlobal ('qz.websocket.connect', [], 'tmp'); JSCallGlobal ('tmp.catch', [JSFunction ('e', 'ajaxRequest (' # 1 ',' 'onError ", {error: e});')]); JSCallGlobal ('tmp.then', [JSFunction ('', 'ajaxRequest (' # 1 ', "onConnected");')]); end; JSCallGlobal is waiting for an object at the end

OK thank you I will test it, as this will be very beneficial in my projects

OK thank you

Problem persists ver 1.70.0.1486 If there is only one record on screen, SelectedRows.Count always points to zero. And the selected record is always locked in the first record of the grid / page

I will test now in version 1.70.0.1486

I am facing a problem with UniDBGrid in version 1.10.0.1472. For some reason that I cannot identify, the grid does not synchronize with the position of the DataSet, and is always parked on the first data record. The grid is selected one record, but the dataset is in another. And when there is only one data record in the grid, SelectedRows.Count always shows zero, even if the record is selected. Is there anything we can do about it?

+1

I think it would be interesting to exchange an idea with the developer of the components

Understand. It could be something related to the component

Tested in uniedit and working perfect with UniEdit1.JSInterface do JSAddListener('afterrender', 'function(){'+ 'this.initResizable({'+ ' minWidth: 100,'+ ' minHeight: 100'+ '}); '+ 'this.bodyEl.setStyle("width", "100%");'+ '}' );

well, thank you

thanks

yes Project1.zip

some other solution

I cannot update the version at this time

Did not work for me v1.10.0.1472 What could it be?

Tente olhar isso

I didn't understand how to use it. I could clarify.

From which version? I'm currently still on version 1.10.0.1472

It would be possible to define a typing mask for the TUniDateTimePicker component and the user does not need to type a / for the date. Because if I type the example: 16012020, the value will not be accepted as valid by the component. You must inform: 01/16/2020