Opened 9 years ago

Closed 8 years ago

#202 closed enhancement (wontfix)

Use System Tray instead of Extended System Tray

Reported by: Yagiza Owned by:
Priority: Feedback Pending Milestone: Qt 4.7
Component: xsystray Version: 4.6.3
Severity: low Keywords:
Cc:

Description

I think, using additional widget just for Qt apps is not a good idea, when we have a fully functional system tray, supported by several applications and Odin, which distributed both as XWorkplace widget and standalone application.
Does it really have lack of functionality, so another system tray implementation is necessary?

Change History (7)

comment:1 Changed 9 years ago by Yagiza

  • Component changed from General to QtGui

comment:2 Changed 9 years ago by dmik

I know only one SysTray? widget, the one from here: http://www.eros2.info/systray_widget_en.shtml. And I described in #44 (comment 7) what limitations it has and why it is not suitable for Qt.

Do you talk about the same implementation or a different one?

Re Odin, please see http://svn.netlabs.org/odin32/ticket/16.

comment:3 Changed 9 years ago by diver

  • Milestone changed from Qt Enhanced to Qt 4.7
  • Priority changed from major to minor

comment:4 Changed 8 years ago by diver

  • Priority changed from minor to Feedback Pending

comment:5 Changed 8 years ago by diver

  • Component changed from QtGui to xsystray

comment:6 Changed 8 years ago by Yagiza

Okay. After examination of Issue #44 I understood that SysTray? from ErOs2 has significant limitations which are really critical for Qt system tray API implementation.
I think the best solution is implementing SysTray? API in XSysTray, so it could fully replace it.
By "fully replace" I mean make it possible for applications which use SysTray? (like PM Downloader) use XSysTray instead. Also, I wold be nice to implement SysTray?'s "display current layer" feature, which displays current keyboard layer's icon as it done in Windows.

comment:7 Changed 8 years ago by dmik

  • Resolution set to wontfix
  • Status changed from new to closed

As #99 mentions in step 4, this is already planned and will be eventually done.

Note: See TracTickets for help on using tickets.