Jump to content

katcharowski

uniGUI Subscriber
  • Posts

    25
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

katcharowski's Achievements

Newbie

Newbie (1/4)

0

Reputation

  1. inclua no clientdataset no campo que você quiser no evento "ongettext" procedure TForm1.numberFieldGetText(Sender: TField; var Text: string; DisplayText: Boolean); begin text := formatFloat( TNumericField( sender ).DisplayFormat , sender.value ); end;
  2. one more problem in this version 1.90: unimpdf frame does not work on some versions of IOS. until Version 1.50 works
  3. does not work 1) using only function window.beforeInit(sender, config) { Ext.util.Format.decimalSeparator = '.'; } result -> allows you to type the point (46.12) but then join them (4612) ------------------------------------------------------------------------ 2) adding UnimDBNumberEdit.JSInterface.JSConfig('decimals', [2]); UnimDBNumberEdit.JSInterface.JSConfig('inputType', ['any']); result -> the decimal point disappears from the keyboard ------------------------------------------------------------------------- 3) adding function painted(sender, eOpts) { var me=sender.inputElement; if (me) { me.dom.setAttribute('inputmode', 'decimal'); } } result -> typing decimal point (46.12), everything appears together (4612) -------------------------------------------------------------------------- 4) using option 1 plus option 3 and deleting option 2 result -> allows you to type the point (46.12) but then join them (4612)
  4. Dear Sir Sherzod, forgive me for pestering you so much, but it was the only contact I had and I had no alternative. as you can see, the problem is not in our project. if you can give me a suggestion of which version could migrate you would be very grateful. Thank you one more time
  5. we noticed that between versions 1.00 and 1.90 there were several very interesting visual changes, and we would not like to return to version 1.00 if that were possible. so I ask you if version 1.50 is similar to 1.90?
  6. similarly in our project, we have numerous screens that have these peculiarities, and all of them stopped working. I opened a ticket but I didn't get any answer. As we cannot continue with this situation, we have to return to a previous version, although we have made several adjustments to version 1.90. If you know, I would like to know if in version 1.50 this too happens. we previously used version 1.00
  7. another test: go to database -> dbcontrols enter a salary with decimal values and you will see that it will record in white. Note: note that the sixth record appears with a blank value, when in fact the value is 33292.94. you can confirm this in dbgrid-> column resize
  8. if you access prime.fmsoft.net/demo/touch/mdemo65.dll, go to dbgrids -> dbgrids editor, select any record, and try to change the salary field to a decimal value, you will get the following result: android, disable the ok button and IOS will record the value without decimals
  9. yes, i use several jedi components without any problem, but i changed to native tdatasource and nothing changed
  10. attached sweeta.pas and sweeta.dfm (as text) with the suggestions you gave. to see the result, access the link and type a number with decimals on a mobile device http://sinteg.com.br/isapi/sweeta.dll/m if you try to popularize clientdataset, the error happens "cannot read property id of null", which also did not find a solution. the data entered in the clientedataset would be necessary for you to see the problem of editing the numeric field, when you double-click on the grid. sweeta.dfm sweeta.pas
  11. I am using this as you guided me earlier, is it in the same place ?? UnimNumberEdit.ClientEvents.ExtEvents
  12. with these settings, the field is now filled, but only with an integer. eg, type 8.57 and return 9
  13. unfortunately it didn't work, even so thanks for the help
  14. our project was totally hampered by this bug, and we are facing serious problems. A call was opened, with no return. Please we need some help. If this error has existed since 24 May 2019, some solution must have existed. Thanks
  15. the same problem was reported By GRFS2000, May 24, 2019 under the heading: TUnimNumberEdit decimal
×
×
  • Create New...