Jump to content

Uwe Raabe

Members
  • Content Count

    228
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by Uwe Raabe

  1. Well, that is what giving number in the enum declaration is, too, The ADD example was just a little joke, because the numbers given nicely add up by coincidence.
  2. Uwe Raabe

    10.3.1 Rio (26.0.332194899) crash

    Yes, definitely! It is just quite some work to do.
  3. Exactly! Anyway, looking into the source is more reliable and usually also faster.
  4. Lately I often use helpers to map those enumerations to their ordinal values. type TEnum = (plough, foo, bar, wtf); TEnumHelper = record helper for TEnum private const FMap: array[TEnum] of Integer = (5, 9, 14, 1000); function GetAsInteger: Integer; procedure SetAsInteger(const Value: Integer); public property AsInteger: Integer read GetAsInteger write SetAsInteger; end; function TEnumHelper.GetAsInteger: Integer; begin Result := FMap[Self]; end; procedure TEnumHelper.SetAsInteger(const Value: Integer); var idx: TEnum; begin for idx := Low(FMap) to High(FMap) do begin if FMap[idx] = Value then begin Self := idx; Exit; end; end; raise ERangeError.CreateFmt('invalid integer for TEnum: %d', [Value]); end; This is pretty simple to use: var enum: TEnum; begin enum.AsInteger := plough.AsInteger + foo.AsInteger; if enum = bar then begin ShowMessage('Hooray!'); end else begin ShowMessage(wtf.AsInteger.ToString); end; end;
  5. As my build machine contains all Delphi versions since XE, I make a simple search for the affected source file and text. I have created a specific search configuration in Total Commander with all the sources folders of the different Delphi installations. That way I only need to specify the file name/pattern and the search text and the time for the search is negligible. This way I can usually figure out which version introduced the change in less than a few seconds. In case the change happened before XE I would have to fire up the old build VM that goes back to Delphi 5, but I rarely have a need for that.
  6. Uwe Raabe

    10.3.1 Rio (26.0.332194899) crash

    This is actually an error in the Navigation Toolbar Keybindings that are integrated in the IDE since Delphi 10 Seattle. It happens when these bindings are not the first in the bindings queue. This error does exist for quite a while when MMX and Castalia are installed side by side in the IDE. As a workaround, make sure that MMX Code Explorer is uninstalled. Start the IDE, disable the Navigation Toolbar Keybindings and install MMX again. Another approach avoiding the uninstall/install cycle requires a bit of fiddling around with the registry: Open the registry and locate the appropriate BDS key. Open Editor -> Options -> Known Editor Enhancements -> MMX.CodeExplorer and set the Enabled value to 0. That will prohibit the MMX keybindings to be registered. Now the IDE should start. When the IDE is running go to Tools -> Options -> User Interface -> Editor Options -> Key Mappings. In the list Enhancement Modules move MMX Code Explorer to the last (bottom) position and enable it again. Hope that helps. The next release will have a fix that assures MMX not overtaking the Navigation Toolbar Keybindings in the first place.
  7. Uwe Raabe

    Solution(s) for coder with quite poor eyesight

    Perhaps the crucial thing is the 100% on the primary monitor? I remember to have seen problems on other systems with a different setting.
  8. Uwe Raabe

    Solution(s) for coder with quite poor eyesight

    At least that is what I see on my system (with Delphi 10.2.3 and 10.3.1). The IDE always designs with 96 dpi even on a monitor with 144 or 192 dpi. I have one 27" 4k Monitor set to either 150% or 200% and two 24" Full-HD ones (primary on 100%). All forms are stored the same (96 dpi) whether designed on any monitor.
  9. Uwe Raabe

    Solution(s) for coder with quite poor eyesight

    As long as the IDE is fully suitable at higher DPI settings, I tend to overwrite the DPI awareness in the shortcut properties to "System (Enhanced)". Although the icons are still a bit blurry, the text is pretty clear. This way the IDE Form Designer will still detect 96 dpi for a DFM internally even when run on a 4K display set to a higher DPI value.
  10. Yes, that is the way it has to be done.
  11. Uwe Raabe

    Property editor - on the finest art

    DesignIntf and DesignEditors. BTW, the ImageIndexMapper makes use of these to replace the ImageIndex properties with the ImageName ones.
  12. Uwe Raabe

    Blogged : Delphi Package Manager RFC

    I do most of my development like that (my Desktop and Taskbar are plastered with Delphi icons). Some IDEs have their libraries set to English language while others are set to German. If you work for different customers you don't want to end up installing a plethora of components into your IDE to cover all those different projects. Often I have to stick with a specific version of components due to customer demand. Have two customers with disjunct demands and you know what @Vincent Parrett is talking about. That said, I guess I belong to the dedicated target audience for such a tool!
  13. Uwe Raabe

    10.3.1 has been released

    The description in that report are not really detailed steps. Even the short hint in one comment is not what I call detailed steps. A good hint is: If it cannot be reproduced it is most likely that the steps are either incomplete or not precise enough. There is almost no day where I don't get a bug report that goes: Do X and you get Y instead of Z! (sometimes they actually mention the expected). Then when I do X as described I usually get Z and not Y. (Just answering one of these now)
  14. I showed this during EKON last year. Unfortunately I couldn't find the time working on it again. It heavily lacks documentation, but perhaps it can serve as a start. https://bitbucket.org/uweraabe/codecoveragemagician
  15. Uwe Raabe

    Error insight in Rio

    No, they probably don't read this Forum. Not sure if they actually read their own one. They read Quality Portal, though
  16. Uwe Raabe

    10.3.1 has been released

    If you can still reproduce it, you should dispute the resolution with detailed steps to reproduce.
  17. A for-in-loop doesn't guarantee some order. Any order seen just relies on the implementation and may be subject to change in the future. (Latest when we compile for quantum computers) I remember someone asking for a backwards for-in-loop, but that request is based on a false assumption in the first place.
  18. Uwe Raabe

    10.3.1 has been released

    Perfect! Then it is actually a regression, which pushes the probability of a timely fix. Now we only need that regression bug report. As the report claims to be fixed in 10.1 Berlin, can someone check if it was introduced in 10.2 Tokyo or one of its updates or in 10.3 Rio?
  19. Uwe Raabe

    10.3.1 has been released

    It is my experience that issues with the installation are usually targeted quickly. I know what you mean, but if we stop filing bug reports to notify them about existing stuff not working they will have more time to add unwanted features. Even if the chances for a filed bug to be fixed are pretty low, they are still higher than those for a bug not filed at all. After all 10.3.1 fixes more than 150 reported bugs, which were probably still not fixed if they weren't be reported in the first place.
  20. Uwe Raabe

    10.3.1 has been released

    What about filing a bug report?
  21. Uwe Raabe

    10.3.1 has been released

  22. For the adventurous of you there is a new download for a MMX Beta version: MMX Beta Setup (current build is 2287) You won't find many new features. The main work was removing unneeded stuff, making use of things not available in older Delphi versions and reorganizing the code. So be prepared to find areas where I accidentally broke something. I would appreciate if you send bugs as email to support@mmx-delphi.de - that way they are automatically added to the bugtracker and are less likely to be forgotten. Feel free to also discuss them here, but even then send that email, so I don't have to duplicate it by hand. Currently there is only one new feature: The MMX Project Options settings have a new check box "Auto Format". If this is checked MMX will execute a format uses clause command every time it adds a new unit to the uses clause. Obviously this only works when the Group and sort uses option is enabled in the Sorting section. Unless something prohibits me to do so, I will announce new builds in this thread.
  23. Uwe Raabe

    MMX Beta 14.1 available

    Build 2289 available: fix: missing images in Entity Insight toolbar fix: scaling problem in About screen fix: problem sending email from support link
  24. Uwe Raabe

    Signing executables

    I am happy with a certificate from ksoftware since a couple of years now.
  25. Uwe Raabe

    MMX Beta 14.1 available

    Seems like this is a relic of former Windows versions. I will skip that check.
×