Existing issues
Problem or use case
Problem or use case
In Win-CodexBar 0.70.0, the dashboard is now tray-flyout-only. The Always on top option solves the problem of the dashboard disappearing when focus moves to another app, but the dashboard can no longer be freely dragged to a user-chosen position on the desktop.
In earlier versions, the separate full dashboard / Show Window mode behaved like a normal desktop window and could be moved and resized freely. That was useful for keeping CodexBar visible in a fixed location while working in other applications.
For users who want CodexBar visible continuously, tray anchoring is restrictive because the dashboard position is controlled by the app rather than the user.
Proposed solution
Proposed solution
Please consider restoring one of these options:
Restore the previous Show Window / normal draggable dashboard mode alongside the current tray flyout, or
Add an option that makes the current dashboard freely draggable and remembers the user's chosen position.
Ideally this would work together with Always on top, so the dashboard can remain visible while the user works elsewhere.
Desired behavior
Dashboard can be dragged to any position on screen.
Position is remembered across closes/reopens and app restarts.
Dashboard can remain visible when clicking another application.
Always on top can remain optional.
Current tray-anchored flyout behavior can remain the default for users who prefer it.
Why this matters
The current 0.70.0 behavior is good for a temporary tray popup, but not for users who keep CodexBar visible as a persistent usage monitor.
The older PopOut / Show Window behavior already provided most of this functionality, so restoring it as an optional mode may be preferable to changing the default tray-flyout behavior.
Version
Win-CodexBar 0.70.0
Windows 11
Related change
PR #712 retired the legacy PopOut layout and made the tray-panel flyout the only dashboard layout.
Affected area
Alternatives considered
No response
Visual details
No response
Additional context
No response
Existing issues
Problem or use case
Problem or use case
In Win-CodexBar 0.70.0, the dashboard is now tray-flyout-only. The Always on top option solves the problem of the dashboard disappearing when focus moves to another app, but the dashboard can no longer be freely dragged to a user-chosen position on the desktop.
In earlier versions, the separate full dashboard / Show Window mode behaved like a normal desktop window and could be moved and resized freely. That was useful for keeping CodexBar visible in a fixed location while working in other applications.
For users who want CodexBar visible continuously, tray anchoring is restrictive because the dashboard position is controlled by the app rather than the user.
Proposed solution
Proposed solution
Please consider restoring one of these options:
Restore the previous Show Window / normal draggable dashboard mode alongside the current tray flyout, or
Add an option that makes the current dashboard freely draggable and remembers the user's chosen position.
Ideally this would work together with Always on top, so the dashboard can remain visible while the user works elsewhere.
Desired behavior
Dashboard can be dragged to any position on screen.
Position is remembered across closes/reopens and app restarts.
Dashboard can remain visible when clicking another application.
Always on top can remain optional.
Current tray-anchored flyout behavior can remain the default for users who prefer it.
Why this matters
The current 0.70.0 behavior is good for a temporary tray popup, but not for users who keep CodexBar visible as a persistent usage monitor.
The older PopOut / Show Window behavior already provided most of this functionality, so restoring it as an optional mode may be preferable to changing the default tray-flyout behavior.
Version
Win-CodexBar 0.70.0
Windows 11
Related change
PR #712 retired the legacy PopOut layout and made the tray-panel flyout the only dashboard layout.
Affected area
Alternatives considered
No response
Visual details
No response
Additional context
No response