Request for review: cbProject::operator=

[oBFusCATed]

Here is the patch: http://cmpt.benbmp.org/codeblocks/patches/cbproject.copy.patch

Why I need this operator - because I need to fix this bug:
1. open project options
2. goto build targets
3. remove a target
4. close the dialog with cancel
5. reopen the dialog

What the user expects is that the target is still there, but in fact it is not, because the dialog works with the original object and not with a copy.
This is not a serious problem when using a modal dialog, but it is when the project options have been moved in an editor.

So any comments about the code will be welcome.

[MortenMacFly]

Well first it does not compile. :-)

It errors at:

Code

        ProjectFile* pf = new ProjectFile(this, **it);

...in cbproject.cpp.

Maybe I am missing something? (BTW: I was very happy to see that the patch applied seamlessly. ;-))

[oBFusCATed]

What is the error?

[MortenMacFly]

I can't try at the moment but if i recall correctly the constructor was missing.

[oBFusCATed]

If you look at the patch it is there.

[Jenna]

@MortenMacFly :
Do you use wx2.8 or wx3 ?
It compiles flawlessly on linux with wx2.8.

@oBFusCATed :
should this already fix the issue with cancelling the properties-dialog ?

[oBFusCATed]

No this is a commit extracted from the middle of my dev branch.

[MortenMacFly]

If you look at the patch it is there.

Mmmh... maybe the patch did not apply completely. :-)

After adding the missing (3) lines its working.

Next time SVN diff patch, please... 

[oBFusCATed]

Next time SVN diff patch, please... 

Sorry but there is no way this could happen. If this is not working for you then I'll just post the link to the branch in git.

[Jenna]

Next time SVN diff patch, please... 

Best solution would be to use a version of patch (either standalone or included in whatever svn-tool you use) that works correctly.
I applied the patch on commandline with the standard patch-utility which ships with Fedora 20 without any problems.

[MortenMacFly]

Best solution would be to use a version of patch (either standalone or included in whatever svn-tool you use) that works correctly.
I applied the patch on commandline with the standard patch-utility which ships with Fedora 20 without any problems.

That's the bottle neck. On Linux there is no issue, for me, too. On Windows you have tones on incompatible patch tools and there is none fully compatible. (I've at least 4 of them for different aspects).

[MortenMacFly]

Sorry but there is no way this could happen.

The way would be through a branch, but I don't want to start this topic again...

But what I wonder is if GIT repos could be sync'ed with a SVN branch?? That would be a nice way to have GIT repos referenced in SVN. I never tried though.

[oBFusCATed]

But what I wonder is if GIT repos could be sync'ed with a SVN branch?? That would be a nice way to have GIT repos referenced in SVN. I never tried though.

I'm not really sure what you're talking about.
But merges in git and svn are incompatible. So if I want to have git-svn cooperation I have to keep my history linear.

The idea of the topic is if you can think of a way this operator= could brake something. I'll post the full changes when I've made it stable enough.

[MortenMacFly]

So... I've no idea whether its related or not, but I've done an SVN update, then applied your patch and since that day C::B freezes for me rather often on Windows. It froze when I opened a settings dialog (editor), when the build completed and just during normal (editing) operation.

Something has become really unstable...

[oBFusCATed]

Try the easiest thing - run cb without my patch. My patch should not cause any problems, because operator= is not used anywhere in the code. And if was used it will be even worse with the old version.