WayfireWM / WayfireWM/wf-shell

command_output_tultip event

Open
#298 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug stale
Dominant language
C++
Stars
179
Forks
55
Avg merge
16d 1h
Merged PRs (30d)
3

Description

In the current implementation the command_output_tooltip event occurs synchronously with the command_output

Expected behavior - event occurs on hover.

For example, in my case, a script was written that displays the tracking of a parcel. The main script was added to autorun, which checks the status after a specified n seconds and writes it to a file. The command_output reads the status file every second. It was planned that when hovering, the tooltip code would work and an unscheduled update of the parcel status would occur and detailed information would be displayed. The detailed information would indicate whether the status had changed at the time of hovering, but this cannot be done since the tooltip code is executed not at the time of hovering, but every second synchronously with the command_output.

I spent a long time looking for an error in my scripts, but after running the tooltip code in the terminal, I realized that it was working and the problem was in the frequency of execution of the tooltip commands

Contributor guide

No contributing guide indexed for this repository

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 tracing the command_output_tooltip event and how command_output updates are scheduled, then compare that path with the hover handling described in the issue. Done means the tooltip event runs when the pointer hovers rather than synchronously with each command_output update.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.