Lajos Juhász

It's in your registered products download page (we were asked not to share the link in this forum).

It's a normal behavior. You should give us more information in order to give us a chance to suggest how could you change the code. If you really have to use dmAutomatic in that case whenever you would like to cancel the drag operation you have to call the EndDrag method with false of the control (in this case the listbox).

Most probably you have to empty the Windows icon cache.

Unfortunately it's not allowed to talk about plans on the Delphi product.

https://docwiki.embarcadero.com/Libraries/Sydney/en/System.Classes.TThread.Suspend Warning: Suspend is deprecated. Pauses a running thread. Suspend was intended to be used by debuggers and is deprecated in RAD Studio XE, in the year 2010. Call Suspend to temporarily halt the execution of the thread. To resume execution after a call to Suspend, call Resume. Calls to Suspend can be nested; Resume must be called the same number of times Suspend was called before the thread resumes execution.

Why would they asked for that? Unlike the roadmap that should not be a secret, someone even paid for the licence key.

It's not required. Delpi 11 and 11.1 is the same (major) release.

You should try with D11.1.

Edit.text is unicode string so you should not use AnsiStrings for that. I tried your FindWordInTextStrUtils and in D11.1 get no deprecated warning: dcc32 command line for "Project1.dpr" [dcc32 Hint] Unit1.pas(30): H2164 Variable 's' is declared but never used in 'FindWordInTextStrUtils' Success Elapsed time: 00:00:00.7

Unfortunately I was able only to find promotion material for decision makers, not technical information for developers. Join the webinar later today and we should learn some information about the Bookmarks.

Should I agree with this Licence?

It's not documented at https://docwiki.embarcadero.com/RADStudio/Sydney/en/Fields_(Delphi). PS. I am also in a couple of minutes will install Delphi 11.1, hopefully I not going to see any new bugs.

Maybe @Uwe Raabe tried to suggest that the beta testers gained access to the repository and instead of QP they were able to check in solution for all the bugs in Jira.

{irrelevant code removed} Most probably is relevant code. We cannot know what is the problem in your code without a simple test case. You're changing the data types of the parameters in your posts. You should post a test application where we can see what are you doing in the function and how you're calling it.

We have no idea as it's most probably sealed by NDA agreement.

There is no need to copy the bytes using the absolute keyword the array and single can share the memory (like I posted).

I was unaware that there is a beta testing (as it usually requires an NDA). In my defense never said that beta testers doesn't do their part of the work. But we already know that usually after the release there is a larger amount of tickets that stay opened. The only information from webinars I have that David Millington was beta testing some unreleased version of C++.

David Millington answered earlier that it will be most probably Delphi 11.1. Next week is the webinar "What's Coming in RAD Studio" there we can expect to get a promise that it will be available as soon as they can compile it (I mean alpha tested for us to do the beta testing).

Now I am stage: Sorry, your userid is required to answer a CAPTCHA question correctly.

In the past couple of weeks happened multiple time. Usually it takes a couple of hours and then you can log in again.

procedure TForm2.ComPort3RxChar(Sender: TObject); var Buffer3 : array[0..14] of Byte; Result3: array[0..3] of byte; s: single absolute result3; lstr: string; begin ComPort3.Read(@Buffer3,15); Move(Buffer3[7],Result3,4); lstr:=s.ToString; end;

You can do the conversion using a record for example: type RfloatBytes=packed record case boolean of true:(floatVal:single); false:(byteVals:array[0..3] of byte); end; var x: RfloatBytes; begin x.byteVals[0]:=%00000000; x.bytevals[1]:=%00000000; x.bytevals[2]:=%01001000; x.bytevals[3]:=%01000001; ShowMessage(x.floatVal.ToString); Or using an absolute keyword to share the memory (this is a Delphi 11 example for older versions you have to convert binary values into decimals or hex values): var x: array[0..3] of byte; s: single absolute x; begin x[0]:=%00000000; x[1]:=%00000000; x[2]:=%01001000; x[3]:=%01000001; ShowMessage(s.ToString); end;

You should construct a search string. Something like this. I believe that Delphi is only coded between 32 and 127 stores as string. procedure TForm1.FormCreate(Sender: TObject); var x: string; i: integer; s: string; begin x:='1Булстат'; s:='Caption = '; i:=1; while i<=length(x) do begin if (ord(x[i])>=32) and (ord(x[i])<=127) then begin s:=s+''''; while (i<=length(x)) and (ord(x[i])>=32) and (ord(x[i])<=127) do begin s:=s+x[i]; inc(i); end; s:=s+''''; end else begin s:=s+'#'+IntToStr(ord(x[i])); inc(i); end; end; edit1.Text:=s; end;

I'm sorry but that is a joke not a roadmap. A couple of years earlier they have had real roadmaps. With information like when will be the next release and what we can expect (sometimes even a couple of minor versions). Now just Now / Next with no information. I'm sorry but that is not enough to plan release cycles and upgrade path for a production environment where you've to plan time for the upgrades in the code base. It's not always enough to install the new IDE, recompile and ship to the customers.

In the quality portal you get response while they validate your report and try to prove it's how the product works and not a bug. After that unfortunately there is no response at all (not even in which version and time frame when the fix will be shipped). Usually you will get no response about the issue at all. Do I think this is the right way? Of course not. As sometimes it's critical to us to know how to communicate with our clients as we have also to plan and communicate to clients when we can ship the fixed product. For some unknown reason who ever decides the future of the product cuts off the communications with the developers (there was a brief period when even on this forum you was able to get honest answers). Instead of a clear communication we can get only promotion materials how everything is nice and shiny (and that's true when you try hello world applications, but as soon as you try to do something more complication you will discover bugs). For me the latest bad sign is that they abandoned the idea that we should have a roadmap. Now you can only read the future of the products only from your coffee mug and that's not a fun thing to do when my managers asks me what is the next step.