Leaderboard

I too miss Rudy, but to be honest he was also the main reason I stopped participating in the old fora; So many interesting topics deteriorated into endless yes, no, yes, no, discussions. That and the misuse of moderation power that were going on killed my interest.

Hello, I have published in github my components to generate charts in uniGUI using de Google Charts API. The components support the following types: Annotation Area Bar Bubble Calendar Candlestick Column Combo Diff Donut Gantt Gauge Geo Histogram Intervals Line Organization Pie Sankey Diagram Scatter Stepped Area Table Timeline Tree Maps Trendlines Waterfall Word Trees The library includes in demos folder the GChartsDemo project with several examples that show how to build the different class charts. When running the demo you can: Display the Delphi Code used to generate the Chart Click Google Guide button to see the official documentation of Google Charts. Click on the Chart to see fired events You can get the source code in https://github.com/JosepPages7/Delphi-GCharts

A few weeks ago I was thinking to myself... boy, do I miss Rudy Velthuis. There's so much I wish I could talk with him about. Then I did some googling and found some archived discussions. I found Rudy and the old, evil version of Nick Hodges arguing that it would be of no benefit at all for Embarcadero to allow users to submit code fixes, also insisting that the Delphi test cases were vast and robust. I was there too, pointing out how useful user-submitted patches have been to open source software, citing the Linux kernel. Then Rudy replied to me that if he had his way, even the Linux kernel wouldn't be allowed to accept code submissions. I drew a few conclusions: Do I still miss Rudy? YES. Was Rudy a very wise and intelligent person to converse with? Yes. Did I enjoy discussing things with Rudy? Yes. Did I enjoy discussing things with Rudy when he got like that? No. It was the toxic environment in the forums that brought people to bombast, rhetoric, refusal to concede points, personal attacks, etc. Do I miss the old forum? NO. Here people can discuss things intelligently without getting nasty or defending a lost cause to the point of being ridiculous. I mean, here we talk about type inference... back on the old forum, I brought up the subject as one of the must-have features for Delphi as soon as possible and one person insisted that type inference was, and I quote, "just the compiler guessing". He continued to insist this after I explained the Handley-Millner Type Inference Algorithm to him, along with its mathematical guarantee of correctness. Then he declared that "a compiler should only do one thing" and type inference would be two things, so it shouldn't be part of the compiler. Another poster went on and on about rejecting modern features in Delphi. Someone asked how they felt about the Delphi string type and they replied that they don't use it where possible, only PChars (!!!). Even Rudy had to concede that this was detrimental and extreme. So... many... weird... conversations there. This place is so much more... sane... in comparison.

This has always been a total heap of crap

Does anyone have an updated version of wuppdi Welcome Page for Delphi 11 Alexandria?

As you likely noticed, Delphi 11 officially does not support Windows XP anymore. You can make your application compatible with XP again by simple set. In Project Options|Building|Delphi Compiler|Linking set "Set OS Version fields in PE Headers" and "Set SubSystem Version fields in PE Headers" to "5.1". Unless your application uses System.Threading.pas (TTask etc) you should run it under Windows XP with no problems. But if so, then you have to tweak this unit. Threading objects actually use in their internals new TThread.GetTickCount64 method, which is hardwired to Windows API GetTickCount64 which is not available in Windows XP API. Take this unit from "source\rtl\common" folder in Delphi 11 installation. Declare new local function in the beginning of implementation section of this unit like this: function _GetTickCount64: UInt64; begin if TOSVersion.Major<6 then Result := TThread.GetTickCount else Result := TThread.GetTickCount64; end; and replace all occurrences of TThread.GetTickCount64 calls with _GetTickCount64. For Win32 applications then copy this modified unit to \lib\win32\debug and \lib\win32\release folders in Delphi 11 installation and rename original System.Threading.dcu to e.g. _System.Threading.dcu. Then build your project which uses System.Threading with Debug and Release configuration. New System.Threading.dcu should be created in mentioned folders. After this you should remove modified System.Threading.pas from these folders to prevent its recurrent compilation. Now your Delphi 11 Win32 applications should run under Windows XP with no External Exception crash.

I would like to read about other users experience upgrading to CB 11 but there is very little without the Embarcadero forums. These are the times I really miss the old Embarcadero forums. Judging the feedback from Delphi users the upgrade is going very well.

I think the OP was referring to having C++ Builder discussions not the forum in general. And I agree with him and for the reason he cited as well. That is, there has just been a major release for C++Builder and there is absolutely zero discussion on it. Very sad. I have not installed it, so I can't comment on it.

HTML Component Library, HTML Editor Library and HTML Report Library version 4.5 released. What's new: 1. RAD Studio 11 Alexandria support. 2. New THtMarkdownPanel component for displaying Markdown documents. 3. Improved Markdown support (tables, links, etc.) 4. Improved rending or large SVG images 5. Improved Flex support. 6. Improved handling of incorrect markup (tag order). 7. Added THtPanel.OnShowResizeHint event. 8. Added THtDocument.EmbedAllImages method for embedding images into document. 9. Added THtPanel.Script property for storing common scripts. 10. Added PrintScale parameter to Print method for scaling pages. 11. Added SplitBlocktoRoot method for splitting nested blocks (f.e. citation in emails). 12. Support for disablet attribute in inputs. 13. Added HighlightCheckedNodes property in THtVirtualXMLTree. 14. Improved scrolling of page with many input controls. 15. Added PNG encoding of pasted images for FMX. 16. New Editor event OnSurrogatePair. This event is called on second (low surrogate) char and when it returns true, default char processing is skipped. 17. SVG: added support for preserveAspectRatio with values none, meet and slice. 18. Faster rendering of large break-all blocks. 19. Support for type="number" in inputs. 20. Added Remove method to JQuery. 21. Addes support for attr!=value selector 22. Added support for summary and details elements. 23. DOCX to HTML conversion is now supported in Delphi 5 - 7. Fixed issues: https://delphihtmlcomponents.com/fixed45.html https://delphihtmlcomponents.com/

In line TImageCollectionSourceItem.Create there is just a call to TWICImage.Create, which initiates a COM call CoCreateInstance. Perhaps there is something wrong with the specific combase.dll on that machine (faulty version, corrupted, infected).

Just to end this thread, I finally got my digital certificate, and I'm signing my applications. I kept a false positive version of the product to test signing it. Well it did work. That version wasn't compiled with DEP or SEH, and signing solved the false positive too. Hopefully this thread will help others

I admit that my conclusion is subjective (just like yours). I should have said: "In the current form it is useless for me".

If you know there's a space in the field, then the code you listed, "Fieldbyname('IntegerField').AsInteger" is misleading as that is most definitely NOT an IntegerField as Integer fields cannot have spaces (well, SQLite might allow it). If your "integer" field might possibly contain values other than integers, you will have no choice but to test to make sure it actually contains an integer before trying to use it as one. The AsInteger function doesn't check the data type, it just assumes you know what you're doing with your database.

Which Database system do you use? Which connection components? If the field in the database is declared as "Integer", it should never contain a Space character. It could be NULL, which means it doesn't contain any value. Most database access components will translate NULL to the value 0, so an empty field should not raise an exception. Which value do you expect in case the field is NULL? To be save, you can test for empty fields yourself: var F : TField; F := Qry.FindField('IntegerField'); if Assigned(F) and (not F.IsNull) then aObject.IntValue := F.AsInteger else aObject.IntValue := -1; // or whatever value you choose in case of an empty field.

Ah, yes, I see now! Wise

It's Python. Perl's conditional operator is the same as C. That looks completely different. And has the condition first. Quote unlike how it is done in Python.

Or even one 😱 ( 🙂 )

That is much easier said than done. While increasing the font size inside a text editor control is usually no problem, doing that in a dialog may destroy the complete layout of that dialog. Having larger fonts in an TEdit will automatically increase the height of the edit, but not its width. A checkbox will even keep its height when the font size changes. Using a larger font inside inside a TRadioGroup also leads to unreadable text. What you suggest would require the scaling of all controls including scaling the complete form. That is exactly what the system scaling is made for. If you want larger fonts in MMX dialogs - increase your system scale. Short answer: No. There are other areas where my free time is probably better spent.

I'm not going to talk about delphi 10.4.2 because I still have 10.4.1. But on sdk, you don't need to use this Embarcadero tool, it is almost always a version behind. Ideally, you should install Android Studio on your own, open it and Configure> SDK Manager and install (download) the latest sdk, get the directory and configure it in your Delphi Options > Deployment > SDK Manager> Android