Leaderboard

Guess what? The new GExperts release is here. There are lots of bug fixes and a few new features in the new version. https://blog.dummzeuch.de/2020/10/23/gexperts-1-3-17-experimental-twm-2020-10-23-released/

In my opinion, using zero based strings is a source of a lot of headaches. I was very upset when Embarcadero introduced that for mobile platform. Now I'm happy they abandoned the idea.

Since there were several questions that this sample doesn't work, I checked myself again. Indeed, it seems to be broken, out-of-the-box. I did the following to get it running: - re-create the project under Rx10.4 - add the Main unit to the project - check the Project/Forms tab, the main form should be auto-created - Removing all unnecessary permissions and entitlements, keeping just Camera permission - For some reason in uMain.pas, this line needed to be added. I have not cxhecked the orginal file again, but maybe there was some non-standard form creation. //21.08.20 added var CameraComponentForm : TCameraComponentForm; - For testing before, I moved the first creation, until the Camera shall be really started. This shouldn't be necessary, but I did that for testing to decouple the actions a little, und keep it in my final. That means you have to press START twice, 1. Get Resolutions, 2. Start camera procedure TCameraComponentForm.FormCreate(Sender: TObject); begin //21.08.20 PermissionsService.RequestPermissions([PermissionCamera], AccessCameraPermissionRequestResult, DisplayRationale); ... procedure TCameraComponentForm.btnStartCameraClick(Sender: TObject); begin //21.08.20 Try get resolutions here at first if cbResolutions.Items.Count = 0 then PermissionsService.RequestPermissions([PermissionCamera], AccessCameraPermissionRequestResult, DisplayRationale) else //only then start the camera with 2nd click PermissionsService.RequestPermissions([PermissionCamera], ActivateCameraPermissionRequestResult, DisplayRationale); end; Et voilâ, camera is working for me. I made some comments already, that I think the non-working samples and demos are a MAJOR SHOWSTOPPER, especially for new customers. If Embarcadero is making a trial, and CE version, they should better take most care that all samples will run out-of-the-box. If new customers trying new tools are a little bit like me, I will DROP the new tools immediately if I cannot get the basic demos and hello worlds running without major quirks. Thats my proof or quality for any software or tool. So its Embarcadero's marketing decision, not mine.

Not so ! Short answer : 0 is not granted to be a random value on all architectures. Long answer : https://software.intel.com/content/www/us/en/develop/blogs/rdrand-do-i-need-to-check-the-carry-flag-or-can-i-just-check-for-zero.html

Most of them. You're scaling a 31-bit integer value in the approximate range 0..X-1 to the range 0..2^64-1 A lot of things wasn't mentioned. For example here's my solution which satisfies all the criteria that was mentioned: The result is 64-bit unsigned. It's cross platform. It compiles with FPC. It's random (for a large enough sample size). and as a bonus It's super fast. function SuperRandom: UInt64; begin Result := 1; end; (sorry - it's Friday)

(Random(X)/X)*High(UInt64)

I really lol'ed at that one - stockholm syndrome anyone?

Hello, I am a member of the support team at CrystalNet Technologies LTD. Let me address the issues and questions raised in this forum. First and foremost, the .Net Runtime Library for Delphi is our flagship product and the most comprehensive library for bridging Delphi and .Net which is used by over 1000 companies and individuals worldwide. The product eliminates much of the complexity of developing Delphi applications with .Net libraries or components, by providing easy-to-use programmable components that facilitate tasks such as hosting .Net CLR in Delphi, access .Net Framework libraries, Load .Net 3rd party DLLs, and many more. The .Net Runtime Library for Delphi contains .Net DLL/WSDL Import Utility for Delphi which helps eliminates the need to manually convert your .Net 3rd-party libraries to Delphi. Competitive Advantages Full access to .Net Framework Class Library (Including new and emerging .NET technologies). No extra dll is required when deployed. No COM registration of .Net Libraries is required when deployed. There are tools to generate your .Net Libraries into Delphi pas files. Allows Delphi to consume .Net libraries as if they were native code. Easy to use. We are currently working on new a product .Net Core Library for Delphi which will fully support .Net Core. At the moment the .Net Runtime Library for Delphi supports only .Net Standard 2.1. For source code examples, go to https://www.crystalnet-tech.com/RuntimeLibrary/ViewRTLExamples https://www.crystalnet-tech.com/DevCodeSamples/Default I understand the confusion surrounding the licenses. The Professional license is interchanged with the Enterprise license. This discrepancy happened way back in 2015 and there are so many clients using the Pro and Enterprise license such that changing it will cause massive problems for them. We know about the issues and we are working on ways to resolve this to ensure smooth transition between Pro and Enterprise licenses for all our clients. If you have further questions, you can send them to us using the link below: https://www.crystalnet-tech.com/contactform.aspx

Hi Marco I can suggest you to implement those features as optional with the possibility of enabling/disabling any of them. This will allow the users to deactivate any of them. I can imagine that Andreas work is more complex because he has to inject the code in a precompiled application so if you integrate those patches in the development code it should be an easier task. Regards

Do you have any actual numbers (compilation time improvement) for any of these. We are gathering some from different developers, and at this point the top one is UnitFindByAlias. Now workaround is stop using unit aliases, but it is our top issue to fix in the compiler. We also have another not in the fix pack that we are rolling out early in a patch, affecting unit cache for large projects and causing compiler time to grow (dramatically!) over successive builds If any other the fixes above (or any not listed) has a very significant effect, we can prioritize it. We are focused on reducing and eventually removing the need of the fix pack, but it takes time as some of the fixes are fairly direct (and many have been implemented in the past) while others require significant rework and spawn threads to do some of the work -- something valuable but requiring extensive testing

10.4 has an update to Bookmarks and Navigator. It creates C:\Program Files (x86)\Common Files\ParnassusShared and places ParnassusBookmarks_XSydney.dll ParnassusCoreEditor_XSydney.dll ParnassusNavigator_XSydney.dll So, to cure the 10.3 ailments, copy from C:\Users\<username>\Documents\Embarcadero\Studio\20.0\CatalogRepository\ to the first mentioned common catalog Bookmarks-1.0\ParnassusBookmarks.dll to ParnassusBookmarks_XRio.dll ParnassusCoreEditor-1.0\ParnassusCoreEditor.dll to ParnassusCoreEditor_XRio.dll Navigator-1.0\ParnassusNavigator.dll to ParnassusNavigator_XRio.dll