KF6 porting. KSelectAction::triggered signal

2024-01-03 Thread Sune Vuorela
Hi I just - during KF6 porting of an app - fall in an api trap: Original code: | connect(d->aZoom, QOverload::of(&KSelectAction::triggered), | this, &PageView::slotZoom); The wrong porting code: | connect(d->aZoom, &KSelectAction::triggered, this, &PageView::slotZoom); The gotcha is that the

Re: KF6 porting. KSelectAction::triggered signal

2024-01-03 Thread Albert Astals Cid
El dimecres, 3 de gener de 2024, a les 9:01:11 (CET), Sune Vuorela va escriure: > Hi > > I just - during KF6 porting of an app - fall in an api trap: > > Original code: > | connect(d->aZoom, QOverload::of(&KSelectAction::triggered), > | this, &PageView::slotZoom); > > The wrong porting code: >

Re: KF6 porting. KSelectAction::triggered signal

2024-01-04 Thread Sune Vuorela
On 2024-01-03, Albert Astals Cid wrote: > scripty has everything checked out so if you tell me what to grep for, I can > run a query on it. I got access to the lxr machine and has been grep'ing there instead, and I only found one maybe-issue that I need to investigate /Sune

Re: KF6 porting. KSelectAction::triggered signal

2024-01-04 Thread Sune Vuorela
On 2024-01-04, Sune Vuorela wrote: > On 2024-01-03, Albert Astals Cid wrote: >> scripty has everything checked out so if you tell me what to grep for, I can >> run a query on it. > > I got access to the lxr machine and has been grep'ing there instead, and > I only found one maybe-issue that I ne