Skip to content

Conversation

IbraheemOsama
Copy link
Member

Adding Column Resizer Control which add resizing functionality to a Grid Column #201
I created the Control and a Sample page to demonstrate the functionality, I added this page to the Samples.json file to be visible in the application.

Waiting your feedback

@msftclas
Copy link

Hi @IbraheemOsama, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@msftclas
Copy link

@IbraheemOsama, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.

Thanks, MSBOT;

/// </summary>
private void Resizer_PointerPressed(object sender, Windows.UI.Xaml.Input.PointerRoutedEventArgs e)
{
if (!_isResizing)
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't there be a CapturePointer call here?

Copy link
Member Author

Choose a reason for hiding this comment

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

I totally removed the pointers events in the new Push

using System.Linq;
using System.Runtime.InteropServices.WindowsRuntime;
using Windows.Foundation;
using Windows.Foundation.Collections;
Copy link
Contributor

Choose a reason for hiding this comment

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

Clear redundant using statements.

@IbraheemOsama
Copy link
Member Author

Interesting Solution, I thought of using converters but I stuck in what should I do in the converter :)
Sure will add the amazing fix to the PR.
Thanks for your help.

@deltakosh
Copy link
Contributor

LGTM!!! Congrats, I know we are picky but the result is great!
Can you go ahead with the doc? :)

@IbraheemOsama
Copy link
Member Author

@deltakosh I finished the documentation and made a merged PR 2 days ago :)

@deltakosh
Copy link
Contributor

Omg...I need to sleep:) we just need another reviewer and we are good to go! Congrats

@deltakosh
Copy link
Contributor

Sorry to ask but we have conflicts here :(

@IbraheemOsama
Copy link
Member Author

There is something wrong please don't merge now :)

@IbraheemOsama
Copy link
Member Author

@deltakosh I resolved the conflicts, class OptionMenuItem was removed and I added it again.

@deltakosh
Copy link
Contributor

Actually this file was removed for true:) we don't need it anymore

@IbraheemOsama
Copy link
Member Author

I removed it :)

@deltakosh
Copy link
Contributor

LGTM

@IbraheemOsama
Copy link
Member Author

@deltakosh @dotMorten What is the next step ? :)

@deltakosh
Copy link
Contributor

Waiting for another review and we merge:)

@deltakosh
Copy link
Contributor

I merged it...Please create issues if you find a problem

@deltakosh deltakosh merged commit 6e42a23 into CommunityToolkit:dev Sep 8, 2016
@deltakosh
Copy link
Contributor

It could be cool if by default the splitter presents the grip icon (even if the user do not specify a content)

@deltakosh
Copy link
Contributor

And we should also think about using your great control for the property grid in the sample app :)

@IbraheemOsama
Copy link
Member Author

@deltakosh Will work on the grip icon and the property grid :)
But I've a small question, I should work on the same forked branch and create a new PR for new features ?

@deltakosh
Copy link
Contributor

A new PR would be perfect:)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants