CODEWITHSUNDEEP
c++qtuser-interface
Anonymous
Anonymous

Reputation: 1560

Singleton or Signal and Slots?

I am trying to reimplement or modify a tab code in a gui application. They are currently using Qt signal and slots system to handle addition and removal of tabs from the tab bar (For example if a tab was being drag from one tab widget to another, the old tab widget will signal the new tab widget that a new tab is coming). I was thinking rather than using that, I could simplify things using a thread safe singleton class. Then when ever a tab is moved, the widget just call on the singleton rather than emitting a signal.

Thanks

Upvotes: 0

Views: 777

Answers (3)

Alexandre C.
Alexandre C.

Reputation: 56956

You want to use a singleton, which will accept messages and dispatch them back ? (note: if you use a garden variety object instead of a singleton, you're essentially implementing an Observer pattern).

Then you are reinventing signals and slots, which use a global state internally. Instead of putting work in reinventing some difficult piece of code, why don't you use the already existing signals and slots ?

Upvotes: 3

Ulrich Dangel
Ulrich Dangel

Reputation: 4625

Don't do that. You are working within an environment and should use the mechanism the framework provides. What about if the UI in the future will have multiple windows and maybe multiple instances?

If possible you should always try to use the way from the framework you are using. This will also help in the future for the maintenance (upgrades, new hires, etc.)

Upvotes: 4

fabmilo
fabmilo

Reputation: 48330

Signals and Slots.

Without even starting why the singleton would be bad, the way the data is updated inside Qt would be messed up by the singleton approach.

Upvotes: 5

Related Questions