13
0

Fix signal emission for Locations::ripple (1/2)

Locations::ripple can never add/remove markers, hence
Locations::changed is not applicable.

That signal is to indicate when more than one location is
added or removed from the location list.
This commit is contained in:
Robin Gareus 2023-12-10 04:08:30 +01:00
parent fe3827b1d8
commit 0f3e3b5243
Signed by: rgareus
GPG Key ID: A090BCE02CF57F04
2 changed files with 2 additions and 6 deletions

View File

@ -277,7 +277,7 @@ public:
void cut_copy_section (timepos_t const& start, timepos_t const& end, timepos_t const& to, SectionOperation const op);
void ripple (timepos_t const & at, timecnt_t const & distance, bool include_locked, bool notify);
void ripple (timepos_t const & at, timecnt_t const & distance, bool include_locked);
XMLNode& get_state () const;
int set_state (const XMLNode&, int version);

View File

@ -1807,7 +1807,7 @@ Locations::range_starts_at (timepos_t const & pos, timecnt_t const & slop, bool
}
void
Locations::ripple (timepos_t const & at, timecnt_t const & distance, bool include_locked, bool notify)
Locations::ripple (timepos_t const & at, timecnt_t const & distance, bool include_locked)
{
LocationList copy;
@ -1846,10 +1846,6 @@ Locations::ripple (timepos_t const & at, timecnt_t const & distance, bool includ
(*i)->lock();
}
}
if (notify) {
changed(); /* EMIT SIGNAL */
}
}
void