inspector's unity_running is not initialized
Bug #719769 reported by
Michael Terry
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
Medium
|
Mikkel Kamstrup Erlandsen | ||
libunity |
Fix Released
|
Low
|
Mikkel Kamstrup Erlandsen | ||
libunity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
unity_running is adjusted as unity goes up and down on the bus, but when the inspector singleton is constructed, unity_running is just set to false. It should check the status at construction time as well.
Makes it rather useless at the moment.
Related branches
Changed in libunity: | |
milestone: | none → 3.4.6 |
Changed in libunity: | |
status: | Fix Committed → Fix Released |
Changed in unity: | |
assignee: | nobody → Mikkel Kamstrup Erlandsen (kamstrup) |
importance: | Undecided → Medium |
milestone: | none → 3.4.6 |
status: | New → Fix Released |
no longer affects: | libunity (Ubuntu Quantal) |
Changed in unity (Ubuntu): | |
status: | New → Fix Released |
To post a comment you must log in.
Well, that would require a sync dbus call. The idea is that you connect to the notify signal on that property to track updates. You need to do that anyway if you plan to make use of that value.
So I guess the solution here is just documentation?