| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
them. They just lead to bugs.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
parents, and they need to exist with a parent in the menu that we're building. So we have to leave the proxy items unparented until they get picked up in the service themselves.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
changes. Using the property call back and just calling that function.
|
| |
|
| |
|
|
|
|
| |
anymore.
|
| |
|
| |
|
|
|
|
| |
track their desktop file paths. So I had to add that little nugget in as well.
|
|
|
|
| |
signal handlers.
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| | |
finalize. Fix by Cody Russell on bug 362124.
|
| |
| |
| |
| | |
to ensure it stays around while we hav signals attached to it. Fix by Code Russell on bug 362124.
|
|\| |
|
| | |
|
|\ \
| |/
|/| |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
also query them in app-menu-items
|
|
|
|
| |
are always below the server that they're associated with.
|