Lajos Juhász

In this case Idera/Embarcadero has no problems. The website used for new customers is working fine. It's just the docwiki that is down that is used only by customers that already paid. Why would they worry? They can get away with no roadmap, no timeframe when the critical errors will be fixed in Delphi. We that already using Delphi should know to work without a proper documentation.

There is no need to panic. It's out for about 2 two weeks. There was a recent webinar from Ranorex that modern IT companies now have a monthly schedule for release. So before we all panic we have just to wait another 2 weeks and see whenever that time frame is used in Idera or not.

I am sure it has System.AnsiStrings unit. The easiest way is to use StrToInt('$1289ABEF').

In that case it's not true anymore check it with: select itemno, count(CustNo) from Vendor where Preferred='Yes' group by itemno having count(CustNo)>1

The PK for Vendor is ItemNo, Custno you cannot make it a unique value only by joining it with fields itemno and preferred. You could use min, max or avg functions.

SQL servers. Parametar cannot be used with like or matches.

I know about problems when trying to debug application built with packages. There are multiple open tickets and now we just have to wait for a solution.

It doesn't working for me. For https://docwiki.embarcadero.com/RADStudio/Alexandria/en/ returns: Sorry! This site is experiencing technical difficulties. Try waiting a few minutes and reloading. (Cannot access the database) Backtrace: #0 /var/www/html/shared/BaseWiki31/includes/libs/rdbms/loadbalancer/LoadBalancer.php(1134): Wikimedia\Rdbms\Database->reportConnectionError('Connection refu...') #1 /var/www/html/shared/BaseWiki31/includes/libs/rdbms/loadbalancer/LoadBalancer.php(749): Wikimedia\Rdbms\LoadBalancer->reportConnectionError() #2 /var/www/html/shared/BaseWiki31/includes/GlobalFunctions.php(2801): Wikimedia\Rdbms\LoadBalancer->getConnection(0, Array, false) #3 /var/www/html/shared/BaseWiki31/includes/cache/localisation/LCStoreDB.php(45): wfGetDB(-1) #4 /var/www/html/shared/BaseWiki31/includes/cache/localisation/LocalisationCache.php(412): LCStoreDB->get('en', 'deps') #5 /var/www/html/shared/BaseWiki31/includes/cache/localisation/LocalisationCache.php(458): LocalisationCache->isExpired('en') #6 /var/www/html/shared/BaseWiki31/includes/cache/localisation/LocalisationCache.php(334): LocalisationCache->initLanguage('en') #7 /var/www/html/shared/BaseWiki31/includes/cache/localisation/LocalisationCache.php(371): LocalisationCache->loadItem('en', 'magicWords') #8 /var/www/html/shared/BaseWiki31/includes/cache/localisation/LocalisationCache.php(292): LocalisationCache->loadSubitem('en', 'magicWords', 'tree') #9 /var/www/html/shared/BaseWiki31/languages/Language.php(3177): LocalisationCache->getSubitem('en', 'magicWords', 'tree') #10 /var/www/html/shared/BaseWiki31/includes/MagicWord.php(352): Language->getMagic(Object(MagicWord)) #11 /var/www/html/shared/BaseWiki31/includes/MagicWord.php(280): MagicWord->load('tree') #12 /var/www/html/shared/BaseWiki31/includes/parser/Parser.php(4848): MagicWord::get('tree') #13 /var/www/html/shared/BaseWiki31/extensions/TreeAndMenu/TreeAndMenu_body.php(24): Parser->setFunctionHook('tree', Array) #14 /var/www/html/shared/BaseWiki31/includes/Setup.php(948): TreeAndMenu->setup() #15 /var/www/html/shared/BaseWiki31/includes/WebStart.php(88): require_once('/var/www/html/s...') #16 /var/www/html/shared/BaseWiki31/index.php(39): require('/var/www/html/s...') #17 {main}

Must be one of your plugins never noticed that problem.

Depending on the database you can try to use TFDEventAlerter (the docwiki at embarcadero at the moment I cannot check for supported databases).

Is the list correct in your example the first numbers are delimited with semicolon while the last is with comma. The easiest way to type this for me is: function ListContains(const PList: string; PNumber: integer): boolean; var sl: TStringList; begin sl:=TStringList.Create; try sl.Delimiter:=';'; sl.DelimitedText:=StringReplace(PList, ',', ';', []); result:=sl.IndexOf(IntToStr(PNumber))<>-1; finally sl.Free; end; end;

You can handle OnMessage for the Applicaton or simple use the OnScroll event of the component.

There is Form7.pb1.Position (a bad design to call directly from another unit as you cannot be sure that the procedure was called from that object) in the code however that's all we can see (besides the problems that the code full of Application.ProcessMessages also that should be avoided).

You've to create a protocol eg. a prefix that will say the following x bytes is a string or a binary data so the reciever can convert the received bytes back.

Even some Unicode arrow characters are not supported by the IDE :(.

It's very simple take a look at TImage.SetBitmap. The TImage object will assign the bitmap to the internal bitmap and will not take the ownership over of the parameter. You've to write: var lbm: TBitmap; begin if OpenDialog1.Execute then begin Image1.Bitmap.LoadFromFile(OpenDialog1.FileName); lbm:=ConvertToGrayscale(image1.Bitmap); try Image2.Bitmap:=lbm; finally lbm.Free; end; end; end;

Maybe this thread can help (I have no experience with thermal printers).

I've also tested: finalValue:=2*index + ResultIsFive(index); the result 9. I guess this is one of the reasons why you should not write procedures with side effects. It can make a mission impossible to find the them.

Changing a DPI can also cause the following error message: --------------------------- Debugger Exception Notification --------------------------- Project XXXXX.exe raised exception class EReadError with message 'Stream read error'. --------------------------- Break Continue Help Copy --------------------------- With call stack: :7538b522 KERNELBASE.RaiseException + 0x62 :030f850a HookedRaiseException + $66 :50162931 rtl280.@System@Classes@TReader@ReadBuffer$qqrio + 0x55 After that the following exception is: First chance exception at $7538B522. Exception class EArgumentOutOfRangeException with message 'Argument out of range'. Process XXXXX.exe (17800) :7538b522 KERNELBASE.RaiseException + 0x62 :030f850a HookedRaiseException + $66 :50159093 rtl280.@System@Classes@TCollection@GetItem$qqri + 0x13 :50159093 rtl280.@System@Classes@TCollection@GetItem$qqri + 0x13 :50cc5327 vcl280.@Vcl@Controls@TControl@Resize$qqrv + 0x1b :50ccac1a ; C:\Program Files (x86)\Embarcadero\Studio\22.0\bin\vcl280.bpl :50ccacec vcl280.@Vcl@Controls@TWinControl@AlignControl$qqrp21Vcl@Controls@TControl + 0x68 :50ccad47 vcl280.@Vcl@Controls@TWinControl@Realign$qqrv + 0x7 :50ccf78c vcl280.@Vcl@Controls@TWinControl@ScaleForPPI$qqri + 0xc8 :50ccf78c vcl280.@Vcl@Controls@TWinControl@ScaleForPPI$qqri + 0xc8 :50ccf78c vcl280.@Vcl@Controls@TWinControl@ScaleForPPI$qqri + 0xc8 :50ccf78c vcl280.@Vcl@Controls@TWinControl@ScaleForPPI$qqri + 0xc8 :50ccf78c vcl280.@Vcl@Controls@TWinControl@ScaleForPPI$qqri + 0xc8 :50ccf78c vcl280.@Vcl@Controls@TWinControl@ScaleForPPI$qqri + 0xc8 :50ccf78c vcl280.@Vcl@Controls@TWinControl@ScaleForPPI$qqri + 0xc8 :50e021a3 vcl280.@Vcl@Forms@TCustomForm@ScaleForPPIRect$qqrip18System@Types@TRect + 0x9b :fffffff8 I don't have a test case for this as I put it on delay and re-testing with D12. Since Embarcadero thinks that it is not relevant to give a valid roadmap I promised to management at the company I work for that this should be fixed in Delphi 12. It's bad that Embarcadero follows the pattern from the past and now entered into the period when they hide every possible information.

Could be RSP-30614 maybe you could update that in D11 it's still not working at all?

There is also RSP-36616 where trace into FD source doesn't work when the application is build with run time packages. Unfortunately it's not confirmed yet from Embarcadero.

Exactly what I was saying. In case you'write: try lObj:=TMyClass.create; finally lObj.Free; end; If the constructor raises the exception the RTL will clear that for you. However in case lObj as the name suggest is a local variable and you didn't assigned nil to it the value will be undefined and calling free on that reference can cause AV (in case you're not lucky that the value was nil).

The only problem with it is that you've to write your code in form: lObj:=TMyClass.Create(....); try ..... finally lObj.Free; end; Anyway you would write it in this form. So there is no problem. I believe it's just another phobia. People can be afraid from correct coding style but will happily use FreeAndNil everywhere in the code.

You missed the example with nested try finally. It should be: LA := TRaiseOnMinus.Create( AInputA ); //<== PossibleRaise try LB := TRaiseOnMinus.Create( AInputB ); //<== Possible Raise try finally LB.Free; end; finally LA.Free; end;