microsoft / microsoft/CsWin32

ACTIVATE_KEYBOARD_LAYOUT_FLAGS enum does not have a [Flags] attribute

Open
#1,664 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
2.5k
Forks
124
Avg merge
1d 3h
Merged PRs (30d)
9

Description

Actual behavior

[A clear and concise description of what the bug is.]
UI.Input.KeyboardAndMouse.ACTIVATE_KEYBOARD_LAYOUT_FLAGS enum does not have a [Flags] attribute

Expected behavior

A clear and concise description of what you expected to happen.
ACTIVATE_KEYBOARD_LAYOUT_FLAGS enum must have a [Flags] attribute

Repro steps

  1. NativeMethods.txt content:
CoInitializeEx
CoCreateInstance
CoUninitialize
LoadKeyboardLayout
GetKeyboardLayout
GetForegroundWindow
GetWindowThreadProcessId
ActivateKeyboardLayout
PostMessage
WM_INPUTLANGCHANGEREQUEST
CLSCTX_INPROC_SERVER
KLF_ACTIVATE
KLF_SETFORPROCESS
IID_ITfInputProcessorProfiles
  1. NativeMethods.json content (if present):
{
    "$schema": "https://aka.ms/CsWin32.schema.json",
    "emitSingleFile": false,
    "className": "WinApi",
    "allowMarshaling": false,
    "useSafeHandles": true,
    "friendlyOverloads": {
        "enabled": true
    }
}
  1. Any of your own code that should be shared?
Context
  • CsWin32 version: 0.3.269
  • Target Framework: net10-windows

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the listed NativeMethods.txt and NativeMethods.json inputs under net10-windows, then inspect the generated UI.Input.KeyboardAndMouse.ACTIVATE_KEYBOARD_LAYOUT_FLAGS enum. Done means the generated enum includes the expected [Flags] attribute for this input while preserving the existing generated API behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.