Skip to content

Conversation

@Simon-IT
Copy link
Contributor

@Simon-IT Simon-IT commented Sep 3, 2019

This is related to my issue 642. In the hit testing by geometry algotithm, the order in which the transformations are crosses is wrong. In the issue 642 there is a project to test in very simple manner the problem.

@ghost ghost added the PR metadata: Label to tag PRs, to facilitate with triage label Sep 3, 2019
@ghost ghost requested a review from SamBent September 3, 2019 10:04
@Simon-IT
Copy link
Contributor Author

Hi, any news about my pull request ?

@weltkante
Copy link

weltkante commented Sep 11, 2019

The issue is classified as 'future' so there is probably nobody looking at it, right now 3.0 release has priority. Maybe get someone looking at the issue first (maybe inclusion in 5.0 is still realistic), looking at the github UI nobody is tracking the PR so you probably won't get an answer here.

@Simon-IT
Copy link
Contributor Author

I hope I didn't make mistakes, but I just wanted to sync my fork with last updates from dotnet\wpf master...

@vatsan-madhavan vatsan-madhavan added this to the 5.0 milestone Sep 13, 2019
@Simon-IT
Copy link
Contributor Author

@vatsan-madhavan When is the 5.0 scheduled for ? We really need it for our WPF CAD product. Isn't really possible for 3.1 ?

@vatsan-madhavan
Copy link
Member

vatsan-madhavan commented Sep 25, 2019

@vatsan-madhavan Vatsan Madhavan FTE When is the 5.0 scheduled for ? We really need it for our WPF CAD product. Isn't really possible for 3.1 ?

5.0 won't release until later in '20. @grubioe is looking into the best way to get this into 3.1 - look for an update from him soon.

@rladuca rladuca modified the milestones: 5.0, 3.1 Sep 27, 2019
@rladuca rladuca added the * NO MERGE * metadata: The PR is not ready for merge yet (see discussion for detailed reasons) label Sep 27, 2019
@rladuca
Copy link
Member

rladuca commented Sep 27, 2019

@Simon-IT Setting NO MERGE until we get 3.1 approval, then we can move forward.

@rladuca
Copy link
Member

rladuca commented Oct 23, 2019

Moving this back to 5.0 since it is based on master, #2103 is the 3.1 port.

@rladuca rladuca added Bug Product bug (most likely) and removed * NO MERGE * metadata: The PR is not ready for merge yet (see discussion for detailed reasons) labels Oct 23, 2019
Copy link
Contributor

@SamBent SamBent left a comment

Choose a reason for hiding this comment

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

The change is good. I have concerns about compat (see #2103), but they are probably only theoretical.

@rladuca rladuca merged commit b57b7bb into dotnet:master Oct 24, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Apr 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Bug Product bug (most likely) PR metadata: Label to tag PRs, to facilitate with triage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants