Forum Replies Created
-
AuthorPosts
-
I maintain several websites and I know that the payments are automatically charged to the credit card. It does not require any action from the site owner as long as the payments go to the service provider.
March 8, 2023 at 9:37 am in reply to: Is anyone able to use AlphaControls with Delphi 11.2 or later? in 64-bit #71125There are many 64-bit issues which ASLR reveals. You can set it to false in linking options until those issues are fixed. See Building > Delphi Compiler > Linking > Support high-entropy 64-bit address space layout randomization (ASLR).
I have fixed some obivous cases by myself where I saw Integer casts done for pointers. Those must be NativeInt casts. But not all, I still have to keep that option False.
I strongly doubt that no one does business with Delphi 5 using Windows XP, but of course I could be wrong.
It will do it automatically as long as the provider receives the money. So sadly nothing can be concluded from that.
February 16, 2023 at 4:43 pm in reply to: Is anyone able to use AlphaControls with Delphi 11.2 or later? in 64-bit #71117Yes, I am using the latest AlphaSkins with Delphi 11.2 64-bit and beta testing 11.3. You need to apply some fixes to make it work. See troubleshooting.
-
This reply was modified 3 years ago by
Lasse.
No contact for months, I am starting to worry if we have any more AlphaSkins development. But the small ones are my worries when you think about what is happening in Ukraine.
Ah, it was mentioned in the title indeed. Delphi 5 was released in 1999. There are certainly several problems with current Windows. I would rather develop with modern Windows and use it to compile the version for the old ones, if needed. XP support ended April 8, 2014. Using XP is very risky. Even Windows 8.1 support ended at the beginning of this year.
PE header tells you what the rest of the file is about. That version is different in modern Windows. I think this is not an issue, if you build in XP with old Delphi version. But when doing the other way around, it must be taken into account.
There is a free community version of Delphi: https://www.embarcadero.com/products/delphi/starter/free-download
It is not the latest version but a significant step from Delphi 5. I’ve come a long way from Turbo Pascal to modern times and there’s no longing to go back.
Which Delphi version you’re using?
I am developing on Windows 11 but I still build versions for XP. I haven’t noticed any issues. I have created own build configurations for XP because with the latest Delphi version (11.2) you need to set PE Header to version 5.1 (two linker options). By default those are in version 6.0 and application will crash on XP with that version.
Have you debugged for example TsAlphaHints.OnCheckTimer procedure? I think there was an issue at some point. I have done 150 fixes for AlphaSkins but none of those affects that…
I have not noticed such behavior. Have you dropped the AlphaHints (TsAlphaHints) component into your application? I see I have done so.
As a Delphi user I am used to compiling and building packages. I see C++ Builder is calling it Make and Build. But I did only build it.
Attachments:
You must be logged in to view attached files.I tried it again, no problem.
Attachments:
You must be logged in to view attached files.I did install the package without any problems (see previous attachment, icon shows it is installed). I was beta testing upcoming Delphi 11.3 thou. I didn’t test this on Delphi 11.2. I haven’t changed any other settings in C++ project files.
Did you build the run-time package first?
-
This reply was modified 3 years, 1 month ago by
Lasse.
Just add vclwinx library and you can build the design package (see attachment).
Attachments:
You must be logged in to view attached files.You can, if you inherit that control and add published Format property. Then just override UpdateFormat and call it when Format property is set.
Embarcadero\Studio\22.0\source\rtl\common\System.ZLib.pas, Line 2850.
You need your own fork for it.
Attachments:
You must be logged in to view attached files.I see that UpdateFormat is setting the format by calling DefDateFormat function:
procedure TsCustomDateEdit.UpdateFormat; begin FDateFormat := DefDateFormat(FourDigitYear); end;That function is getting the format from default Windows format settings as you can see here:
function DefDateFormat(NormalYears: Boolean): string; var Y: ShortString; begin Y := iff(NormalYears, 'YYYY', 'YY'); case GetDateOrder({$IFDEF DELPHI_XE}FormatSettings.{$ENDIF}ShortDateFormat) of doMDY: Result := 'MM/DD/' + Y; doDMY: Result := 'DD/MM/' + Y; doYMD: Result := Y + '/MM/DD'; end end;So, if you want to use different date format than your Windows settings you need to modify that function or make UpdateFormat virtual (it is protected but not virtual) and inherit the control. You need to also add DateFormat property, it seems to be private.
TsCustomDateEdit = class(TsCustomComboEdit) protected procedure UpdateFormat; virtual; public property DateFormat: string[10] read FDateFormat write FDateFormat;Then you could do your own control like:
TMyDateEdit = class(TsDateEdit) protected procedure UpdateFormat; override; ... procedure TMyDateEdit.UpdateFormat; begin DateFormat := ... end;I see there are a lot of Integer casts. All pointer or object references should be casted to NativeInt.
That is a Windows feature… So, there must be some 64-bit math issues in AlphaSkins code which are causing it to fail.
-
This reply was modified 3 years ago by
-
AuthorPosts