winapi | Minimal but useful Lua bindings to the Windows API

TMainMenu is just a thin wraper around default windows functionality. You can't change its position. But you can replace it with TActionMainMenuBar. This one can be moved to TTitleBarPanel.

Although I still don't understand the cause of the problem, with the help of @IInspectable's guidance and documentation, I was able to prevent the window from being activated by processing the WM_MOUSEACTIVATE message. The updated window procedure is as follows.

You can check out the authentication API in this document, which describes several authentication sections (Credentials Management, LSA Authentication, Network Provider API, Smart Card Authentication, SSPI, Winlogon and Credential Providers), and here is an introduction to using Windows Authentication in C#.

I think what you might be looking for is a hook of type WH_JOURNALRECORD.

With this, the callback procedure that Windows will call in response to the various events that this hook intercepts is of type JournalRecordProc, and the lparam parameter passed to this function points to an EVENTMSG structure, which looks like this:

DLGTEMPLATEEX is a special case. In fact, there is no structures with such a name in the wndows headers. If you want to use a structure, you must create you own, with custom array sizes.4

Example

This looks suspicious:

The answer is exactly what I knew it would be.

• i started with headers translated by Franck Soranio
• where some definitions were packed records
• when that didn't work, I tried adding $ALIGN 8 - the ABI required by Windows
• when that didn't work, I tried adding packed to all records

When that didn't work, i asked Stackoverflow.

In the meantime, i spun up Visual Studio C++, and compared the sizeof of the original structures, and the Delphi translations.

They didn't match.

The problem was the packed records.

• sizeof(EVENT_TRACE_LOGFILEW): 416 bytes (was 404)
  • sizeof(EVENT_TRACE): 88 bytes (was 80)
    • sizeof(EVENT_TRACE_HEADER): 44 bytes (was 40)
  • sizeof(TRACE_LOGFILE_HEADER): 272 bytes

Removing the record packing fixed it.

The algorithm is described in the Microsoft Extensible Firmware Initiative FAT32 File System Specification. Download fatgen103.doc

The technique chosen to auto-generate short names from long names is modeled after Windows NT. Auto-generated short names are composed of the basis-name and an optional numeric-tail.

The Basis-Name Generation Algorithm

The basis-name generation algorithm is outlined below. This is a sample algorithm and serves to illustrate how short names can be auto-generated from long names. An implementation should follow this basic sequence of steps.

1. The UNICODE name passed to the file system is converted to upper case.
2. The upper cased UNICODE name is converted to OEM.
   If (the uppercased UNICODE glyph does not exist as an OEM glyph in the OEM code page) or (the OEM glyph is invalid in an 8.3 name)
   {
   Replace the glyph to an OEM '_' (underscore) character.
   Set a "lossy conversion" flag.
   }
3. Strip all leading and embedded spaces from the long name.
4. Strip all leading periods from the long name.
5. While (not at end of the long name) and (char is not a period) and (total chars copied < 8)
   {
   Copy characters into primary portion of the basis name
   }
6. Insert a dot at the end of the primary components of the basis-name iff the basis name has an extension after the last period in the name.
7. Scan for the last embedded period in the long name.
   If (the last embedded period was found)
   {
   While (not at end of the long name) and (total chars copied < 3)
   {
   Copy characters into extension portion of the basis name
   }
   }
8. Proceed to numeric-tail generation.

The Numeric-Tail Generation Algorithm

If (a "lossy conversion" was not flagged) and (the long name fits within the 8.3 naming conventions) and (the basis-name does not collide with any existing short name)
{
The short name is only the basis-name without the numeric tail.
}
else
{
Insert a numeric-tail "~n" to the end of the primary name such that the value of the "~n" is chosen so that the name thus formed does not collide with any existing short name and that the primary name does not exceed eight characters in length.
}

The "~n" string can range from "~1" to "~999999". The number "n" is chosen so that it is the next number in a sequence of files with similar basis-names. For example, assume the following short names existed: LETTER~1.DOC and LETTER~2.DOC. As expected, the next auto-generated name of name of this type would be LETTER~3.DOC. Assume the following short names existed: LETTER~1.DOC, LETTER~3.DOC. Again, the next auto-generated name of name of this type would be LETTER~2.DOC. However, one absolutely cannot count on this behavior. In a directory with a very large mix of names of this type, the selection algorithm is optimized for speed and may select another "n" based on the characteristics of short names that end in "~n" and have similar leading name patterns.