Jump to content

Lars Fosdal

Administrators
  • Content Count

    3335
  • Joined

  • Last visited

  • Days Won

    110

Posts posted by Lars Fosdal


  1. One could measure the time between the events to decide if they should be coupled - but ... lots of extra work. IMO, the Alt should normally be pressed BEFORE the click, and released AFTER the click-release - although you could interpret it as the Alt status only being required/captured at the time of the initial click, and only use the click-release as completion event.

    • Like 1

  2. https://quality.embarcadero.com/browse/RSP-41961

     

    The process of cleaning up circular references can be quite challenging, as we today have no good tool to discover and track the unit interdependcy.  "Blatant" circular references are explicitly forbidden, but since we can include units both in the interface and the implementation section - it is quite easy to circumvent this rule.

     

    Another challenge is when you inadvertently drag in a massive collection of units into your project, because someone needed a structure or function from a specific unit - which again uses other units, which uses others again - and so forth.

     

    The discovery of where this unit is included, and when in the compilation it is parsed, would be significantly helped by a simple build log. A sequential log of the compilation of each unit in the application - indicating where it first was necessary to  compile another unit to complete the current unit.

     

    I suggested it could look something like this - more comments in the QP issue.

    Pls vote/comment if you find it interesting.

    unit1 compiling... 
       unit2 compiling... 
         unit3 compiling...
         unit3 compiled (lines, warnings, hints)
       unit2 compiled (lines, warnings, hints)
    unit1 compiled (lines, warnings, hints)

     


  3. Does the clients access the DB directly, or is there a service between the clients and the db?

    If direct access, you have to take extra care in your design of the backup - to avoid clients making partial changes during the backup.

     

    It is not a trivial problem you have here...


  4. Is the DB a single instance on a server, accessed by multiple users?

     

    There are several strategies, but it is hard to say which one is the right one without insights into how your DB is setup and used.

    https://blog.devart.com/mysql-backup-tutorial.html

    https://dev.mysql.com/doc/refman/8.0/en/backup-and-recovery.html

     

    Your application could probably be installed from scratch, but what about application configuration?

    Stored locally in file or registry? 

    Complex config or simply a URI to the DB + credentials?

     

×