Jump to content

GPRSNerd

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

7 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Here's one of many: https://quality.embarcadero.com/browse/RSP-22230
  2. Check the linefeeds of your source file. When you have a mix-up of CR and/or LF this might happen. Also errors when compiling show on the wrong line number and other spooky stuff...
  3. Known problem with Rio 10.3. There are several unfixed bugreports at Embarcadero.
  4. GPRSNerd

    Read of address DEADBEE7. - Source of this raise?

    Programmers jokes, there exist a couple of these "HEX speak" or "magic number" addresses: DEADC0DE, DEADBEEF... https://en.wikipedia.org/wiki/Hexspeak I use them as constraints in unittesting to check that a peer or protocol is using the expected values. So the programmer wants to tell you something...
  5. GPRSNerd

    IDE Fix pack for Rio

    OK, figured it out myself. dcc32.exe -> dcc32compiler.exe dcc32.de -> dcc32compiler.de I've left dll and jdbg as original and it works.
  6. GPRSNerd

    IDE Fix pack for Rio

    Hmmh, the current set of files for 32bit is named slighty different, as a suffix is used: dcc32.exe dcc32260.de dcc32260.dll dcc32260.jdbg What do I have to rename them to exactly?
  7. GPRSNerd

    Rio.1 does not save all layout settings

    Same happens here as well, you have to resize it everytime the IDE is restarted.
  8. GPRSNerd

    10.3.1 has been released

    So that it is also ignored as all the other high voted bug reports, that will probably never be fixed? It seems to be more important to add unwanted features than to get the existing stuff working.
  9. Reason is, that the path to the core dll is common for all installed releases through a setting in the registry: [HKEY_CURRENT_USER\Software\Parnassus OU\Core] "Path"="C:\\Users\\Public\\Documents\\Embarcadero\\Studio\\20.0\\Experts" This always points to the last installation.
  10. Aeemmhhh, you're actually showing the button with the half-moon glyph in your screenshot!
  11. It's "hidden" in den application titlebar. Click on the "moon" icon on the right of the titlebar and you'll see..
  12. GPRSNerd

    CCR.EXIF: Rio throws E2574

    I've solved it so far by using the orginal type declaration for compilers >= Rio. It might not be the most elegant solution, but it keeps up the spirit of the original code (I hope). {$IF CompilerVersion >= 33} {$DEFINE GenericTStringDynArray} {$IFEND} TIPTCStringArray = {$IFDEF GenericTStringDynArray} Array of String {$ELSE} type Types.TStringDynArray {$ENDIF}; //using 'type' means the helper defined below will only apply to it <OT> How to get rid of the empty quote object? </OT>
  13. GPRSNerd

    CCR.EXIF: Rio throws E2574

    TStringDynArray is declared as TArray<string> instead array of string now...
  14. Hi, I'm trying to get my components, packages and units running under Delphi 10.3 Rio. Currently I'm stumbling over CCR.EXIF (latest revision 1.5.1), the set of units to read and manipulate EXIF header data and such in images. The compiler throws a E2574 in the unit CCR.Exif.IPTC.pas at this place: unit CCR.Exif.IPTC; interface uses Types, SysUtils, Classes, {$IFDEF HasGenerics}Generics.Collections, Generics.Defaults,{$ENDIF} {$IFDEF VCL}Jpeg,{$ENDIF} CCR.Exif.BaseUtils, CCR.Exif.TagIDs, CCR.Exif.TiffUtils; type TIPTCStringArray = type Types.TStringDynArray; //using 'type' means the helper defined below will only apply to it {$IFDEF XE3+} TIPTCStringArrayHelper = record helper for TIPTCStringArray class function CreateFromStrings(const Strings: TStrings): TIPTCStringArray; static; function Join(const Separator: string): string; end; {$ENDIF} In line 11 of this excerpt the compiler throws a E2574 ("Instantiated type can not be used for TYPE'd type declaration") about the use of "type" for this declaration of TIPTCStringArray, which shall extent TStringDynArray with a recordhelper. This error doesn't occur with any compiler prior to Rio. When I leave out the "type" it compiles fine. I'm not an expert on generics and such, so I'm not sure what consequences it has to just leave out the "type" (in contrary to the authors intent according to the comment). Has anyone a better idea what to do here?
×