Skip to content

Add active launch indicator to launch history menu#2652

Open
SougandhS wants to merge 1 commit into
eclipse-platform:masterfrom
SougandhS:LaunchActive
Open

Add active launch indicator to launch history menu#2652
SougandhS wants to merge 1 commit into
eclipse-platform:masterfrom
SougandhS:LaunchActive

Conversation

@SougandhS
Copy link
Copy Markdown
Contributor

@SougandhS SougandhS commented May 5, 2026

Adds support to show an active launch indicator in the launch history menu, helping users quickly identify which launch configurations are currently running from launch history. Entries with associated non-terminated launches are marked with a visual indicator "●" ,Once the indicator is shown, users can immediately recognize that the configuration is already running, helping avoid unnecessary or unintended clicks from the launch history menu.

With Active (Running)
image
image


With In-Active (Terminated or not launched) image

@iloveeclipse
Copy link
Copy Markdown
Member

Since recently the "circle" was added to indicate changed file, I would not use this for running launch config, it would be confusing.

What about simple "(running)" label?

@SougandhS
Copy link
Copy Markdown
Contributor Author

What about simple "(running)" label?

I went with this first, but It felt bit long...

image

@SougandhS
Copy link
Copy Markdown
Contributor Author

Since recently the "circle" was added to indicate changed file, I would not use this for running launch config, it would be confusing.

How about \u25B8 ?

image

@iloveeclipse
Copy link
Copy Markdown
Member

iloveeclipse commented May 5, 2026

How about \u25B8 ?

How about \u2699 ( ⚙ "gear" ) or \u1F3C3 ( 🏃 "running man" ) ?

@SougandhS
Copy link
Copy Markdown
Contributor Author

How about \u2699 ( ⚙ "gear" ) or \u1F3C3 ( 🏃 "running man" ) ?

Gear looks great !
image
Pushed this change

\u1F3C3 ( 🏃 "running man" )

this doesn't render 😅

@iloveeclipse
Copy link
Copy Markdown
Member

The change is simple and nice, do we really need an option for that? If yes, please enable by default.

@akurtakov
Copy link
Copy Markdown
Member

If unicode symbol is to be used - extra testing is needed that the chosen one is widely available in default fonts as per (https://eclipse.dev/eclipse/development/plans/eclipse_project_plan_4_40.xml#target_environments) and ideally in some popular fonts(whatever they are) and last but not least verify on all platform that nothing bad happens when a font that doesn't contain the symbol is used.

@akurtakov
Copy link
Copy Markdown
Member

The change is simple and nice, do we really need an option for that? If yes, please enable by default.

Please no option for such things. We already have more options than one can find and manage.

@SougandhS SougandhS force-pushed the LaunchActive branch 2 times, most recently from 18c45c7 to e2949db Compare May 5, 2026 14:16
@SougandhS
Copy link
Copy Markdown
Contributor Author

The change is simple and nice, do we really need an option for that? If yes, please enable by default.

Please no option for such things. We already have more options than one can find and manage.

Removed all the preference parts 👍

@SougandhS
Copy link
Copy Markdown
Contributor Author

If unicode symbol is to be used - extra testing is needed that the chosen one is widely available in default fonts as per (https://eclipse.dev/eclipse/development/plans/eclipse_project_plan_4_40.xml#target_environments) and ideally in some popular fonts(whatever they are) and last but not least verify on all platform that nothing bad happens when a font that doesn't contain the symbol is used.

Thanks, I'll try to check in these platforms..

@iloveeclipse
Copy link
Copy Markdown
Member

If unicode symbol is to be used - extra testing is needed that the chosen one is widely available in default fonts

See also https://stackoverflow.com/questions/48468088/unicode-character-uncompatibility

At least on RHEL 9.6 with "Sans Serif" dialog font (whatever system means with that name) it looks OK.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

Test Results

    54 files  ±0      54 suites  ±0   33m 48s ⏱️ - 2m 41s
 4 667 tests ±0   4 645 ✅ ±0   22 💤 ±0  0 ❌ ±0 
11 895 runs  ±0  11 742 ✅ ±0  153 💤 ±0  0 ❌ ±0 

Results for commit 2d58afb. ± Comparison against base commit a372a8c.

♻️ This comment has been updated with latest results.

@SougandhS
Copy link
Copy Markdown
Contributor Author

Hi @iloveeclipse, @akurtakov, how about adding overlay image ?
image image

@iloveeclipse
Copy link
Copy Markdown
Member

how about adding overlay image ?

Why not, but then maybe the one with the green "Run" arrow like on the Progress view icon?

@akurtakov
Copy link
Copy Markdown
Member

I have a preference to (widely spread) unicode symbol as (at least on Linux) these autoadjust contrast on changes of Gtk theme. Also they are less resource hungry and auto managed by OS instead of images that have to be destroyed and etc.

@iloveeclipse
Copy link
Copy Markdown
Member

So let's try with \u2699 ( ⚙ "gear" ) and push it to M3 so hopefully more people could test it. If someone complains, we can switch it off for RC.

@SougandhS
Copy link
Copy Markdown
Contributor Author

So let's try with \u2699 ( ⚙ "gear" ) and push it to M3 so hopefully more people could test it. If someone complains, we can switch it off for RC.

So include a preference option ?

@iloveeclipse
Copy link
Copy Markdown
Member

no, just merge & check for bug reports. worst case is some rectangle shown instead I assume.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds UI decoration to the launch history (favorites + history) drop-down menu so that entries corresponding to a currently active (non-terminated) launch are visually marked, helping users avoid relaunching already-running configurations.

Changes:

  • Fetches current launches from the launch manager when building the launch history menu.
  • Decorates matching launch history/favorite entries by appending a Unicode indicator.
  • Introduces a helper method to detect whether a configuration has an associated non-terminated launch.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@SougandhS SougandhS force-pushed the LaunchActive branch 3 times, most recently from 46a02a6 to b891428 Compare May 7, 2026 06:56
@eclipse-platform-bot
Copy link
Copy Markdown
Contributor

This pull request changes some projects for the first time in this development cycle.
Therefore the following files need a version increment:

debug/org.eclipse.debug.ui/META-INF/MANIFEST.MF

An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch.

Git patch
From f4e66b505001ea89996fdacdf5446cf0cb56a650 Mon Sep 17 00:00:00 2001
From: Eclipse Platform Bot <platform-bot@eclipse.org>
Date: Mon, 1 Jun 2026 02:48:53 +0000
Subject: [PATCH] Version bump(s) for 4.41 stream


diff --git a/debug/org.eclipse.debug.ui/META-INF/MANIFEST.MF b/debug/org.eclipse.debug.ui/META-INF/MANIFEST.MF
index 8c8a0b29b7..489122e563 100644
--- a/debug/org.eclipse.debug.ui/META-INF/MANIFEST.MF
+++ b/debug/org.eclipse.debug.ui/META-INF/MANIFEST.MF
@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %pluginName
 Bundle-SymbolicName: org.eclipse.debug.ui; singleton:=true
-Bundle-Version: 3.21.0.qualifier
+Bundle-Version: 3.21.100.qualifier
 Bundle-Activator: org.eclipse.debug.internal.ui.DebugUIPlugin
 Bundle-Vendor: %providerName
 Bundle-Localization: plugin
-- 
2.54.0

Further information are available in Common Build Issues - Missing version increments.

Adds a visual indicator to launch configurations that are currently
active in the launch history menu.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants