![Delphi-PRAXiS [en]](https://en.delphipraxis.net/uploads/monthly_2018_12/logo.png.be76d93fcd709295cb24de51900e5888.png){kind=logo}
All Activity
This stream auto-updates
- Today
-
Please pardon my ignorance here but I haven't 'deployed' fastdcc before. hat is the process to deploy pls? Do I simply run fastdcc32.exe in the file and like idefixpack it will extract and install itself, and I presume fastdcc32hok.dllx, in the appropriate place? I only install the 32bit stuff. How do I check/confirm it is installed correctly? Regards & TIA, Ian
- Yesterday
-
(Mis-)Behaviour of TStringHelper
FredS replied to Cristian Peța's topic in RTL and Delphi Object Pascal
LastIndex and DownRange would help but honestly, this is like having to flip your steering wheel when you shift the car into reverse. 🙂 -
And another development snapshot is available. This time the functions in StyleUtils.inc (Vcl.Styles) got optimized what makes the UI rendering faster. IDEFixPackD103RegDev.7z fastdccD103vDev.7z
-
(Mis-)Behaviour of TStringHelper
Attila Kovacs replied to Cristian Peța's topic in RTL and Delphi Object Pascal
It's a bullsh@t. The doc is a big ~, the mimicked java/.net implementation is a ~, and the parameter name "startIndex" is a ~. It should be called lastIndex as the function name reflects only an index lookup, and not any search in some direction, and mostly not the underlying implementation. -
Array compression in InternalGetUnicodeCategory() (System.Character)
mael replied to mael's topic in RTL and Delphi Object Pascal
Thanks a lot for your input, Mahdi. I wanted to post working code once it's finished and polished, but that will take a while, as I have to solve other parts of the software first. Your solution is somewhat similar to what I tried, however this is limited to values <= UInt16 (as you noted), whereas Unicode code points range from 0 to $10FFFF. The other issue is that while TUnicodeCategory was in the question, I wanted to implement a general solution, where ranges aren't necessarily as regular (lookup tables for other properties of codepoints where they don't build such nice ranges) or working with the specifically chosen "hash keys" that will not work when your ranges are not as good. Ideally I was looking for an algorithm that automatically searches for the proper hash functions that would yield a reasonably small hash table. Or at least a principle algorithm for it. I'll have a look at your solution again, though, if I need to optimize my approach further. -
Rio Dark Theme and the structure panel
David Hoyle replied to Sherlock's topic in Delphi IDE and APIs
This is similar to this QP I raised: https://quality.embarcadero.com/browse/RSP-22221 I don't use the structure pane so I don't know whether that was affected at the time. -
We use DUnitX and it discovers all our silly mistakes before release
Daniel replied to Lars Fosdal's topic in DUnitX
I have moved the discussion about the TStringHelper into a separate topic: https://en.delphipraxis.net/topic/738-mis-behaviour-of-tstringhelper/ -
@Sherlock I mean "Aussteigen, Einsteigen, Geht" 😄
-
I suspect the real thing here is that maybe you used a more modern RTL or different project settings so the potential bug became an exception. Turn checking on in debug builds! /D
-
The new Dev version works perfectly. Thanks!
-
(Mis-)Behaviour of TStringHelper
FredS replied to Cristian Peța's topic in RTL and Delphi Object Pascal
Yeah, certainly made clear in the documentation </sarcasm> One would hope that when they copied a DotNet function they could at least copy the DotNet explanation: The search starts at a specified character position and proceeds backward toward the beginning of the string for the specified number of character positions. At this point the claim that it works as expected needs to come with new documentation. -
(Mis-)Behaviour of TStringHelper
Stefan Glienke replied to Cristian Peța's topic in RTL and Delphi Object Pascal
Sorry I meant startIndex + Length(searchText) - 1 because the method simply works as follows: it starts to search at startIndex but does not consider any character in the string after that. That causes it not finding any searched text that extends beyond that index. So as Christian already stated it basically works as if you cut the string after startIndex. So what the documentation is simply missing is the fact that it would not find any occurence that extends past startIndex when you use any of those overloads, that's all. -
(Mis-)Behaviour of TStringHelper
FredS replied to Cristian Peța's topic in RTL and Delphi Object Pascal
True but it is the same as IndexOf, should I now file a bug report for IndexOf? StartIndex specifies the initial offset in this 0-based string where the search starts Because this does not compute: Assert(s.IndexOf('Hello', 38) = s.LastIndexOf('Hello', 38)); I originally looked at the source and also took " startIndex - (Length(searchText) - 1)" into account but here is that math: // 0 19 38 0-based s := 'Hello how are you, Hello how are you, Hello how are you'; // ^ 32 Startindex - (Length('Hello')- 1), searched forward or backward? IMO at this point the claim that it works as expected needs to come with new documentation or a bug fix. -
Thanks DummZeuch, that is what I suspected and have started modifying the code as you suggested. The routine contains a lot of code so it is going to take a while. As I mentioned, the original code was written around 1998 (using Delphi 1, believe it or not) and back in 2014 I was contracted to convert the application so something that would compile in W7. I had to replace all of the ReportSmith reports but unfortunately, for one big key report they had used a reporting product called formGenWin which went out of business around 2006. I obtained as much of the source code of the product that was available, the latest in D5. The bank in their wisdom didn't want to spend the time and money to have me re-write the old report to allow later versions of Delphi. However, the code seemed to work without any exceptions until this t time (under MS 7, done on two years cycles) so I suspected an MS update to have something to do with this problem. This problem came up under MS7, I believe, but I am running MS10 on my machine. I will have to check with them to see what O/S they were using when this blowup occurred. Hopefully, I can get the error to disappear by doctoring the code as you suggest.
-
They are defined as 'Double' inside of an object, so yes they are floating point. If I had done the original code, I would have used integers.
-
So...this is what my structure panel looks like... I know low contrast seems to be a cool thing these days, but this is ridiculous. After searching QP for a while I didn't find an existing issue for this and created one: https://quality.embarcadero.com/browse/RSP-23756 On a side note, the panel headers are very large and cost quite some space...sadly not configurable.
- 1 reply
-
- 1
-
-
😄 Nah, AEG ceased to be AEG a long time ago.
-
öööööööö, if not, you could try an AEG. 😉
-
advi joined the community
-
Everything worked out fine. Took more than an hour, because after upgrading to 10.14, macOS discovered there is something called 10.14.3 available, and installing that took some time again. Delphi-wise I still can't use the 64Bit iOS-Simulators, but apart from that, everything is A-OK.
-
Object inspector in Rio 10.3.1 looses a changed property value when selecting an other component
PeterBelow replied to Tom Mueller's topic in Delphi IDE and APIs
It's a VCL issue. I noted another yesterday: if you type text into a property (like caption) that is longer than what fits into the visible width of the OI column the text does not scroll while you type to keep the caret in view. -
How do I find out in which Delphi version a certain RTL/VCL change was implemented?
A.M. Hoornweg replied to A.M. Hoornweg's topic in RTL and Delphi Object Pascal
Never mind, I've found an easier way to find it out. Look at this page : http://docwiki.embarcadero.com/Libraries/Rio/en/Help_of_Previous_Versions This page lets me browse the help file wiki for older Delphi versions (starting with 2010). I simply navigated to the unit of interest for a specific Delphi version, such as this one: http://docwiki.embarcadero.com/Libraries/XE7/en/System.AnsiStrings ... and by simply replacing the "XE7" in the link for older versions, I was able to ascertain that function "searchbuf" first appeared in the Ansistrings unit in Delphi XE4. Problem solved! -
Best way to validate posted data and return validation errors
Andrea Magni replied to Marco Breveglieri's topic in MARS-Curiosity REST Library
You are welcome. We may consider adding some kind of (light) validation to the serialization/deserialization mechanisms. I like to keep MARS lightweight but something like "this field is required" could be safe to implement. -
FMX.WebBrowser + Rio 10.3.1 = net::ERR_CLEARTEXT_NOT_PERMITTED
Magno replied to Magno's topic in FMX
Thank you for all information!! I will test it and let you know! EDIT: Solved!!!! Thank you! -
Best way to validate posted data and return validation errors
Marco Breveglieri replied to Marco Breveglieri's topic in MARS-Curiosity REST Library
Hi Andrea, thank you very much for all the information provided, really far more than I hoped for. I only need to verify the presence of some mandatory fields and the range of some values, nothing complicated. My question originated from the fact that I am used to validation mechanisms embedded in other frameworks, such as ASP.NET MVC, and so I wanted to check if there was something ready to use inside MARS that would provide the same benefits, e.g. field attributes or similar. I think the second implementation is a good balance between clarity and effectiveness so I will implement my validation code following that sample. Thanks again for your great support! Marco. -
Delphi 5 FOR Loop problem (W10-64bit)
Primož Gabrijelčič replied to mjwallin47's topic in General Help
It uses "banker's rounding", after all. 😉
