46161c3af0
Taking the completion widget as an argument was overly complex. The process now looks like: 1. CompletionView gets deletion request 2. CompletionView passes selected index to CompletionModel 3. CompletionModel passes the row data to the owning category 4. The category runs its custom completion function. This also fixes a bug. With the switch to the hybrid (list/sql) completion model, the view was no longer updating when items were deleted. This fixes that by ensuring the correct signals are emitted. The SQL model must be refreshed by running the query. We could try using a SqlTableModel so we can call removeRows instead. The test for deleting a url fails because qmodeltester claims the length of the query model is still 3. |
||
|---|---|---|
| .. | ||
| test_completer.py | ||
| test_completionmodel.py | ||
| test_completionwidget.py | ||
| test_listcategory.py | ||
| test_models.py | ||
| test_sqlcategory.py | ||