I'll need to test this patch. Probably in the weekend.

Tested and working on mac

Yes, if someone is forcing a int is because he knows what he is doing (or
not).
In either case, if you are using a int as argument the compiler will not
accept.

Are this patch rebased on master ? It appears to be not.

They are const variables inside the scope.

In D13780#284403, @rizzitello wrote:

Why ? and why only for these two

• plugins: Add missing emit

• testclient: Use mult args QString in arg

I think that everything is ok, but I would prefer others review to see if this PR is suitable. I have my doubts

In D13258#271798, @rizzitello wrote:

In D13258#271797, @patrickelectric wrote:

In D13258#271795, @rizzitello wrote:

Thinking something like..

ttyS0 ? How is that possible ?

idk this is just there with my ryzen machine

In D13258#271795, @rizzitello wrote:

Thinking something like..

I think that is a nice thing to have in atelier, but not in atcore widgets. Everything else appears to be ok (layout and code).

Everything appears to be fine now, but we need to test before pushing. Please ping me in the weekend to do it.

rebase

The app was crashing in the start, this patch solve the problem.
I'll try to put more love in Kamoso, maybe watching multiple cameras at the same time (I'm working with stereo cameras here).

foo
{

for(...)
{

In D12675#257835, @laysrodrigues wrote:

@patrickelectric Kate has a view manager, that changes the factory when something changes see https://github.com/KDE/kate/blob/master/kate/kateviewmanager.cpp#L610
As you can see to activate a new view it removes the previous one.

In D12675#257791, @laysrodrigues wrote:

@patrickelectric The problem is that since we dont remove the views, they start to have conflict and the files are not managed properly by KTextEditor and guiFactory(Main Window).
See the discussion on telegram.