Jump to content

Uwe Raabe

Members
 View Profile  See their activity

  • Content Count

    2907

  • Joined

  • Last visited

  • Days Won

    169

Posts posted by Uwe Raabe

  6. Posted · Edited by Uwe Raabe

    Reading the code despite of its irritating formatting reveals the problem: 

      WorkOrdersSelectedRow := WorkOrdersGrid.Selection.Top;
  if FWorkOrderManager.GetWorkOrderDataByIndex(WorkOrdersSelectedRow - 1, Data) then
    // evaluates file index
    FileIndex := ARow - 1;

  if (FileIndex < 0) or (FileIndex >= TWorkOrderData.FILE_DATA_SIZE) then
    Exit;

    FileIndex will not be initialized when the if clause fails.

     

    BTW, it also irritates that the compiler is charged guilty first.

    • Like 14

  16. Posted

    The plethora of working Delphi programs are proof that there already exist concepts to eliminate dependencies between units. They may differ from those available in other programming languages, though.

     

    IMHO, circular dependencies should be eliminated even if they appear in implementation sections and thus making the code compile. I wouldn't support any request to extend that in any way leading to more circular dependencies.

    • Like 6

  20. Posted

    17 minutes ago, Lajos Juhász said:

    On the other hand, it does not work for the Bookmarks or the Parallel debugger

    So they seem not to be able to manage it even when they hire the developer. 

     

    21 minutes ago, Lajos Juhász said:

    The only thing that could be better in theory is integration. They would see what could be improved to make it work better.

    Obviously that is more wishful thinking than perception of reality. I simply cannot see anything like that going to happen in the foreseeable future.

     

    BTW, I still even refuse to provide MMX via GetIt for several reasons.

    • Like 2
    • Sad 1

  21. Posted

    5 hours ago, Berocoder said:

    Have there ever been any talk with Embarcadero about use MMX Explorer instead?

    At least back then they had no interest.

     

    Current state:

    • it is actively maintained
    • it is available for a couple of recent Delphi versions
    • it is free for all Delphi SKUs

    Would you bet on all that not going to change?

    • Thanks 1
    • Sad 1

  22. Posted

    I always try to get my projects on the most recent versions as soon as they enter a state where I can benefit from the features while being able to tame the defects. The less active a project is, the larger gets the gap between the used version and the recent one. Nevertheless, also these projects are moved to newer versions, albeit on a slower rate.

     

    Some customer projects have to stay on older versions, either due to decisions out of my realm or lack of demand for maintenance and enhancements. Whenever either becomes necessary I also try to get this on a newer level. Usually the costs for that cancel out with the higher effort of maintaining it with the older version.

     

    Whenever I am forced to work with any of these older versions (mostly D2007 or XE2) I immediately realize why I always prefer to avoid doing so.

×