Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Geo)Group behavior changes #2759

Draft
wants to merge 37 commits into
base: main
Choose a base branch
from
Draft

Conversation

realthunder
Copy link
Collaborator

Thess patches are split out from #2723

Please refer to this post for description of group changes.

@haraldg
Copy link
Contributor

haraldg commented Jun 9, 2020

Hi, I'd like to test this, as is supposedly fixes a rather important issue in Arch. (Easy to work around but very confusing to new people.)

Can you rebase and resolve the merge conflicts?

@realthunder
Copy link
Collaborator Author

Can you rebase and resolve the merge conflicts?

Done. Please try.

@haraldg
Copy link
Contributor

haraldg commented Jun 17, 2020

Hi @realthunder, I'm seeing an issue that I believe is related to this PR:
In the Arch WB, when drawing a wall directly (ie just click the wall tool and draw the base line), I get the following error message:
410.371 <App> Document.cpp(3500): Unbenannt#WallTrace still touched after recompute

This PR is the only change I have on top of master, so I guess it is responsible.

@realthunder
Copy link
Collaborator Author

Is it possible to attach a file showing the problem?

@haraldg
Copy link
Contributor

haraldg commented Jun 17, 2020

Github tells me "We don't support that file type" for an .FCStd, so I have renamed it to .zip, but it is utterly trivial anyway: Just an empty file with a single wall.

Wall.zip

@realthunder
Copy link
Collaborator Author

The problem is caused by not fixing direction of the line segment in WallTrace. It behaves the same in upstream.

@realthunder
Copy link
Collaborator Author

BTW, ArchWall is not a group. So this patch shouldn't have any effect on it. It is more relevant to ArchBuildingPart, I guess.

@haraldg
Copy link
Contributor

haraldg commented Jun 18, 2020

That's strange, I never saw this before. I need to compile current master again ...
Thanks for your input.

@haraldg
Copy link
Contributor

haraldg commented Jul 19, 2020

I have used this branch now for a all my work for a full month. I can confirm that it fixes a nasty problem for the Arch WB. I didn't run into any regressions. I'm switching back to master now, as the branches have conflicts again and it is unlikely that my testing will uncover any regressions in the future.

I'm sorry that I don't have the insight into the code base to do a code review, but I'm looking forward to when this gets merged.

@berndhahnebach
Copy link
Contributor

berndhahnebach commented Aug 4, 2020

link to the forum post with the nasty bug described ...
https://forum.freecadweb.org/viewtopic.php?f=23&t=38779&start=20#p340174

link to this PR as a fix:
https://forum.freecadweb.org/viewtopic.php?f=23&t=38779&start=50#p369903

@pwnorbitals
Copy link

Is there a blocking issue with this PR ? Not sure why we don't merge (after rebase/resolve)

}
}
}

App::Extension::extensionOnChanged(p);
}

void GroupExtension::slotChildChanged(const DocumentObject &obj, const Property &prop) {
if(&prop == &obj.Visibility && !_togglingVisibility)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reading this code, I wonder: Shouldn't this &prop == &obj.Visibility be kept? I'm not entirely sure, but it looks like the below handler only has code for when a child's visibility changes? Or is this changed handler somehow limited to only Visibility changes now?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it is limited to Visibility. A new signalChanged has been added to every property. This slotChildChanged is now hooked to child objects' Visibility.signalChanged, so no need to check for property anymore.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I see it was in an earlier commit (57e2164), I was looking just in the same commit. Ok, looks good, thanks for clarifying!

}
}
return false;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really like these helpers, great for readability of the other code. However, I would personally put these helpers, along with modifications to use them in existing code, in a separate commit, which would then make no functional changes, just optimize the existing code, making both resulting commits easier to review. It's of course not up to me and I believe that the form/separation of these PRs has already been discussed a lot, but just wanted to add my 2c here :-)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@berndhahnebach berndhahnebach added Core Issue or PR touches core sections (App, Gui, Base) of FreeCAD and removed For 0.20 labels Sep 17, 2021
@berndhahnebach
Copy link
Contributor

berndhahnebach commented Sep 24, 2021

Following a link to the branch on the CI-repository:

https://gitlab.com/freecad/FreeCAD-CI/-/commits/PR_2759

The CI-status is available on the latest commit of the branch.
If there is no status available the PR should be rebased on latest master.
Check pipeline branches to see if your PR has been run by the CI.

https://gitlab.com/freecad/FreeCAD-CI/-/pipelines?scope=branches

@berndhahnebach
Copy link
Contributor

Would it be possible to rebase on latest Master? Cheers bernd

@realthunder
Copy link
Collaborator Author

Yes, sure. I'll rebase all of my PRs. But since there are quite a few of them. It'll take some time.

@donovaly
Copy link
Member

donovaly commented Jan 6, 2022

can you please rebase to merge the PR?

approved once by @yorikvanhavre .
@chennes , @wwmayer any concerns from your side?

@donovaly
Copy link
Member

Will this PR become part of the planned Toponaming inclusion branch?

@pwnorbitals
Copy link

@realthunder pinging for rebase as I think it's a very interesting PR. Thanks ! :)

@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@FreeCAD FreeCAD deleted a comment from freecadci Jul 5, 2022
@berndhahnebach
Copy link
Contributor

pipeline status for feature branch PR_2759. Pipeline 574892903 was triggered at 193d88e. All CI branches and pipelines.

@realthunder
Copy link
Collaborator Author

PR suspended for now, and will resume after topo naming merge.

@luzpaz luzpaz added the ✋ On hold This PR must not be merged before some condition is met label Nov 15, 2022
@luzpaz luzpaz marked this pull request as draft November 15, 2022 03:42
@maxwxyz
Copy link
Collaborator

maxwxyz commented Apr 27, 2024

Is this PR also ready to be resumed after the recent toponaming merges?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core Issue or PR touches core sections (App, Gui, Base) of FreeCAD ✋ On hold This PR must not be merged before some condition is met
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Set Visibility/Invisibility of object that requires manual intervention (not simply Space bar)