Note that there are some explanatory texts on larger screens.

plurals
  1. USCraig Young
    primarykey
    data
    text
    plurals
    1. CO@Rapunzo: If you already have a number of forms in your project, an extra one isn't going to make much difference. Just make sure you manage it appropriately depending on how it will be used. I.e. Create it at startup or on demand? Keep it or recreate it on every use? Allow multiple instances or only one? ..... That said, if you really are striving for an extremely light-weight app, Delphi is probably not the best choice; but 99% of the time the overhead is relatively insignificant, and the benefits you gain make it all worthwhile. (See Rob Kennedy's answer)
      singulars
    2. COHi Edwin, we experienced a similar problem to you; and also opted for the same kind of workaround. We know our problem is due a 3rd party component suite that calls `Application.ProcessMessages`. This particular component suite is in general poorly written (i.e. this is not the only problem); as such we have decided to phase the component suite out of our systems. (We'll probably leave the 'workaround' in plaec though, because it really should not be possible to fire a UI event while the same one is busy processing. - No matter what the cause!)
      singulars
    3. COWhenever someone creates an object instance they call a function to return the new instance. This function (usually called Create or CreateXXX) is a special kind of function (a constructor); but a function nonetheless. So whenever someone calls such a Create function, it is their responsibility to manage the resource (I.e. destroy the object when necessary). TIP: Do not call your procedure ` procedure **Create**BibleNames(aStrings: TStrings); ` ... because that is **NOT** what it's doing.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload