Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

19 Good

Technical Information

  • Delphi-Version
    Delphi 10.2 Tokyo

Recent Profile Visitors

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

  1. @Dalija Prasnikar Good to hear that with Fmx we're not the only hopeless bunch of people out there, and all others face similar issues. But your' reight, XCode e.g. fixes most issues by itself, and I wigh Delphi could have that state of smartness too. Regarding above "old code" line, thats true. IMHO the only reliable way to keep old code running is to separate code parts into many quite small, well testable fractions. Much more code-modularization is needed than it would be necessary for traditional Windows development. Its good coding practice anyway, so we have to have even more discipline maybe.
  2. Record destructors are a brand new feature sind 10.3 Rio. Do you really want to use it already ? http://blog.marcocantu.com/blog/2018-november-custom-managed-records-delphi.html http://docwiki.embarcadero.com/RADStudio/Rio/en/New_features_and_customer_reported_issues_fixed_in_RAD_Studio_10.3
  3. Well Dave, I think I owe you a beer. Thank you very much for pointing me in the right direction. I already made such proposal earlier, why is it so hard to find workarounds in the web. Wouldn't it be about time to have a kind of "CanIUse" and "Polyfills" for Delphi ? I would rather look into a well sorted database of workarounds, instead of searching Google first. If anybody at EMBT (or elsewhere) is listening to me, I hope there could be such a valuable search structure too (maybe here in DP as well).
  4. Hi , I ran into another iOS problem, which I thought was solved in 10.3 Rio. Since I updated some iPhone and iPad to iOS12.13, the Location doesn't seem to fire any more. I was sure this was fixed before, but now it seems to strike back. System(s): Rx10.3 Rio Ent, iPhone/iPad iOS12.13 Problem: The location sensor doesn't send OnLocationChange events at all, while all other events, like OnHeadingChanged are there. When starting the "Allow" selection appears, but that doesn't start actions. Workarounds tested: I followed the advices to add NSLocationAlwaysAndWhenInUseUsageDescription in newer iOS, also following the nice instruction here from FeLDMARShaL, which is probably the essence of all other descriptions found in the web. http://fire-monkey.ru/topic/5393-ios-полноценная-фоновая-работа-приложения/#comment-34184 and the description and demo from DelphiWorlds https://www.delphiworlds.com/2016/02/location-sensor-work-in-the-background-on-ios-9/ The solutions described were simple: just add "NSLocationAlwaysAndWhenInUseUsageDescription" key, but that doesn't seem to work always. In my tests neither the Emba samples, not the DelphiWorlds sample seems to work any more. Does anybody has a clue what else is missing ? Rollo
  5. I don't think a preliminary "guess" might help, when e.g. TryStrToFloat() fails. It is maybe only a general switch on what is the preferred method to use. Even if the guess is valid, and you have only ONE wrong decimal number, you have to handle the TryStrToFloat() failure anyway. So what ?
  6. Hi , does anybody know more deeply about what Apple plans for the new "teams" restructurization ? https://developer.apple.com/support/teams/ Is this an iTunes case only, or does this affect the MemberCenter teams too ? How would this affect RadStudio anyhow, as we're using "personal teams" and "company agents" in the MemberCenter ? I'm afraid this could affect the provisioning files, and the RadStudio way of reading and analysing the provisioning data. I hope this is not one another Apple "improvement" which causes too much headache for developers. Maybe some insiders could already peek inside whats going on at Apple .
  7. I would add a little more safety anyway, to ensure that you' in a number at all, e.g. like _s[i-1].IsSpace or _s[i-1].IsDigit _s[i+1].IsSpace or _s[i-1].IsDigit and probably if you find the first dot in a new number, just analyse this number until the end. I assume this would give a little more stable results, to avoid things like "a,b,c,d" counting wrong.
  8. Rollo62

    FireDAC.Phys.FB causes e2597 in Android 28

    On mobile I would recommend Sqlite, its small, preinstalled and less "headache" DB.
  9. Rollo62

    FireDAC.Phys.FB causes e2597 in Android 28

    If you can use Sqlite, its working fine. Take care to remova any FB reference, even unused, to avoid this msg.
  10. Rollo62

    Rio quality disappoint

    Would be a consideration to use IDE for views only, and setting all events via code. Would bring your design more close to MVVM too, as a side effect .
  11. @PeterBelow That looks alittle to much copying for simple task, from my point of view. Ok, its possible, but i See no advantage beside thats low is still there. The current string is Not immutable in my case, but a subresult from a former function call, where i want to modify the 1. Char in a second step..
  12. @Der schöne Günther Yes immutable strings are fine, if I want to use them. But it seems that then the only possible to re-build the whole string, if I only want to change one character. @Stefan Glienke ZBS = OFF would be a hard choice, which I want to avoid, it would be not necessary just for my simple, single case now. The Low/High solution works fine, but I'm aware now that removing all 1-based strings causes probably some unexpected performance issues.
  13. Sorry, its just a little off-topic, but I think fits well to this discussion ... As always in life: by chance I just got the case that I wanted to change the 1. char in a string. I stumbled into that this 0-based method didn't work, since .Chars is read only LStr.Chars[0] := LStr.Chars[0].ToLower; So I have to fall back to the High/Low solution here LStr[Low(LStr)] := LStr[Low(LStr)].ToLower; Is this right, that TStringHelper for 0-based strings doesn't offer any solution to replace single characters, beside the Low/High solution ? This is a little disappointing, because I was changing new code to 0-based StringHelper but now it seems that there is a solution missing for single-char handling. The TStringHelper function which I expected to solve this, TStringHelper.Replace(), does seems to have a different purpose. So I think I still have to rely on Low/High for a while, instead of moving to a clear, common 0-based handling for all cases.
  14. @Uwe Raabe thanks for the info. So I can stay with Length, and hope that EMBT doesn't change arrays to 1-based, one sunny day
  15. Absolutely right. German engineers use their hands for more important stuff