Jump to content

dummzeuch

Members
  • Content Count

    1680
  • Joined

  • Last visited

  • Days Won

    49

dummzeuch last won the day on October 12

dummzeuch had the most liked content!

Community Reputation

929 Excellent

Technical Information

  • Delphi-Version
    Delphi 2007

Recent Profile Visitors

3338 profile views
  1. dummzeuch

    Hot Reload in Delphi?

    I use it often to repeat a call to a function where I missed something when stepping trough the first time. Works without a problem for this and saves the time to restart the processing. e.g.: SomeCodeHere; try SomeFunctionCall(SomeParameters); // <== Code raised an exception I need to investigate except on e: Exception do LogException(e); end; SomeMoreCodeHere; // <== so I place a breakpoint here // (after the debugger stopped on the exception) // and then set the execution point back to the function call Of course after that the call stack may be broken, but usually I stop the process anyway to fix the problem.
  2. Looks like you are using GExperts. If yes, turn off the "Goto Previous Modification" and "Goto Next Modification" experts and see whether that solves the problem.
  3. While I agree with you that that's the best use of limited resources, the promise of supporting older versions as part of the subscription still stands, and we paid for it. One could call that a breach of contract.
  4. dummzeuch

    The state of GExperts Support for Delphi 11

    One or multiple monitors? Which resolution and DPI?
  5. dummzeuch

    GExperts 1.3.19 Alpha for Delphi 11

    There is a now an installer for version 1.3.19 Alpha of GExperts for Delphi 11.
  6. dummzeuch

    The state of GExperts Support for Delphi 11

    There is a now an installer for version 1.3.19 Alpha of GExperts for Delphi 11.
  7. dummzeuch

    The state of GExperts Support for Delphi 11

    I'm making progress with the dockable forms. The custom drawn listboxes in both, the Editor Bookmarks and the Grep Results form should now be drawn correctly on high DPI and low DPI monitors. Other dockable forms will probably be broken now while they looked OK before. This also fixed some issues for non DPI aware versions of GExperts. Also I think the drawing errors for comboboxes should now be fixed. One major headache that's left are the icons on toolbars. They get lost when moving a form between two monitors with different DPI. No idea yet, how to fix this.
  8. Not sure I understand what you mean here. Which pointer are you talking about? And why do you think it's being reset? Depending on how the reader is implemented Seek would read a record from a file (already with a buffered stream) or from an internal data structure. In this particular case it just accesses data already read into an array. It is serious in this case. The data in that file (and those associated with it) would be unusable and processing it should be stopped.
  9. That name is based on the Seek function for a file of record. Usually the reader (we have many of these for various file types) is a thin wrapper around a file of record. Depending on the file type that "thinness" varies though.
  10. dummzeuch

    D11 - A bridge too far.. :-(

    Why should they? There apparently are enough people who pay the full price for the privilege of becoming beta testers. And I have to include myself in that. (OK, it's not my own money. I wouldn't pay for this.)
  11. I think "shouting" would be a better word for what you mean. But I agree. My Comment usually looks like this: if bla then Exit; //==> Not quite as "loud" but at least a bit more visible than a simple "Exit"; Of course, given structural highlighting this is not quite as important nowadays as it was on the olden days.
  12. I for one prefer "Egyptian begin/end". And I like the name. 😉
  13. dummzeuch

    D11 - A bridge too far.. :-(

    Who says that they weren't? You left out the important second part of my sentence: "... and should have been fixed before the release "
  14. dummzeuch

    D11 - A bridge too far.. :-(

    Many of the still existing problems should have been found during the beta tests and should have been fixed before the release. The current state of D11 should be considered public beta, not ready for production, but they charge for it (quite a lot). It's a hen and egg problem really: E.g. The VCL designer is not usable in the current state (IMHO), so why should one use it? But if nobody uses it, the bugs will not be found, reported and fixed.
  15. In general, you are right. In that case I would have called the function TryGetFirstValidEntry or something similar. In this particular case it is an error if there is no valid entry. This method was only added because the first entry did not have a valid time which caused an error elsewhere. We added a search for the first valid entry because of that. If there is none, some manual action is required. Thinking about this: The method should probably be called GetFirstValidEntry rather than SearchValidEntry. Break and Continue are considered special cases of Goto by some (and I tend to agree because they usually decrease readability).
×