| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The correct time to remove custom widgets is precisely
after we checked if the panel can be activated, and before
creating the panel. We were not following that, and it was
causing the panels with header widgets to never actually
show their custom widgets.
Fix that by calling remove_all_custom_widgets() at the
correct point in panel creation.
|
|
|
|
| |
This will help in debugging.
|
| |
|
|
|
|
|
|
|
|
|
| |
When moving from and to different views, the first row
might be activated due to focus going to the listbox. This
wasn't a problem before because we couldn't hit that code
path, but now we can.
Fix that by always selecting the first visible row.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
There are a couple of small problems with the search
behavior here. First, if we select a panel from search
and leave it, it will continue to stay there forever.
Second, if panels change their visibility status during
runtime, the panel list wouldn't respond accordingly.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When changing panels, CcWindow can only remove the previous
panel's header widgets after making sure the new panel was
successfully set.
However, this is not the case, and when the current panel
fails to be set, the previous panel's header widget is
removed.
Fix that by waiting to remove the header widgets until the
panel is successfully set.
|
| |
|
|
|
|
| |
It's WIP.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Static init functions are functions that initialize resources
or monitor daemons without needing any contextual information,
such as a CcPanel instance or access to a CcShell implementation.
These functions are meant to be used for monitoring a panel's
visibility, when it makes sense. Usually, panels that represent
hardware that potentially is not available or is not supported
should hide itself.
Following this commit, the Wi-Fi panel panel will be adapted as
the first user of this new API. Other panels that require this
functionality will be adapted later.
|
|
|
|
|
|
| |
This field can be used to communicate the visibility of the
panel from a static context (i.e. without any instances of
a CcPanel nor any access to CcShell).
|
|
|
|
|
|
|
|
|
|
|
| |
In order be able to modify panel information statically,
we need to have access to the CcShellModel from static
functions. CcApplication, thus, is a better place for the
model to live, since we can access it outside any scope
using g_application_get_default().
It also makes sense from the modeling point of view, since
the model is not tied to the shell anymore.
|
|
|
|
|
| |
This is just an almost-trivial commit that ports
CcPanel to use the latest code practices around.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
No functional changes were introduced. This is purely
aesthetical.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit improves the Night Light code in various
ways:
* Turn it into a template class, subclass of GtkDialog,
and adapts all the code to reflect that.
* Update the code style in various places, to make it
more conformant with the documented code style.
* Reorganize the code a bit, moving functions around,
to make it more conformant with the documented order.
|
|
|
|
| |
Let's use modern code practices around.
|
|
|
|
|
| |
This adds tests for the VPN section. Note that the tests to check
sorting are disabled currently as sorting is not implemented.
|
|
|
|
|
|
| |
Also wait for the connection-added signal instead of only waiting for the
property notification for the connections. While not neccessary, this is
more correct.
|
|
|
|
|
| |
In preparation for testing VPN sorting. Looks for a parent of a specific
type.
|
|
|
|
|
| |
This simply ensure the section does not randomly show up after making
unrelated changes.
|
|
|
|
| |
Just a small code cleanup in the network panel test code.
|
|
|
|
|
| |
Having a delete_cb to handle connection removal is useful for other
tests. Add the function in preparation for VPN testing.
|
|
|
|
|
| |
The add_cb can be useful in other tests. Return the remote connection in
the info struct to allow its use in other situations.
|
|
|
|
|
|
|
|
| |
Doing so means we handle the same events as the panel. This probably
makes no difference, but this way it is guaranteed we are not getting
weird inconsistencies during testing.
Also fixes a NMClient memory leak in the process.
|
|
|
|
|
| |
This adds support for waiting on an NMConnection object and also allows
waiting for both signals and properties.
|
|
|
|
| |
This is in preparation for adding VPN related tests.
|
|
|
|
|
|
| |
If there are no connections or devices then we should not be showing
e.g. the Bluetooth list. Add a simple check that this is handled
correctly.
|
|
|
|
|
|
| |
This has the side effect of showing UI elements that should not be
visible at startup. Just add the correct gtk_widget_show calls to show
all relevant widgets.
|
|
|
|
|
| |
Otherwise the test might run on a develpers wayland session rather than
using the created X11 server.
|