This is a migrated thread and some comments may be shown as answers.

Double Click event on Row of RadGridView

58 Answers 2969 Views

GridView

This is a migrated thread and some comments may be shown as answers.

This question is locked. New answers and comments are not allowed.

58 Answers, 1 is accepted

answered on 28 Jan 2010, 06:51 AM

Hi

Did you mean you are tring to attach event handler on gridview's row?

Please look the code below :

    
            (this.GridView as RadGridView).AddHandler(  
        
            GridViewCell.MouseDoubleClickEvent,  
        
            new EventHandler<Telerik.Windows.RadRoutedEventArgs>(this.OnDoubleClick));  
        
            private void OnDoubleClick(object sender, Telerik.Windows.RadRoutedEventArgs e)  
        
            {  
        
                    .....your logic    
        
            }

And you shoud add Telerik.window.controls.dll to your project. hope this help

Regards,
Eum

answered on 04 Jun 2010, 02:38 PM

gridviewrowdoubleclick.zip

Hello Tom Wire,

Please find attached a solution that shows how to handle a double click event of GridViewRow.

Best wishes,
Yavor Georgiev
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

answered on 18 Aug 2010, 09:07 PM

Hello troy,

That's the general idea of routed events in Silverlight and WPF - they climb up the visual tree so that in the end the control that handles the event gets hit whenever that event fires for any control below it in the visual tree. Handling LeftMouseButtonUp on your GridView or even UserControl is fine. You just have to check if the element in which the event originates is the one you need and only then take action.

Besides, if you try to manually attach handlers to row objects, this will play merry hell with virtualization.

All the best,
Yavor Georgiev
the Telerik team

answered on 07 Jun 2011, 03:36 PM

Is it possible to use this method to always get the value of a specific cell within the clicked row? I've been using something like this on the cell double click, but now have a requirement that clicking anywhere on the row should return the one cell's value:

// handling the MouseDoubleClick event of the RadGridView

void OnGridMouseDoubleClick(object sender, MouseButtonEventArgs e)

{

FrameworkElement originalSender = e.OriginalSource as FrameworkElement;

object oTest = sender.GetType();

if (originalSender != null)

{

var cell = originalSender.ParentOfType<GridViewCell>();

if (cell != null && cell.Column.UniqueName == "CaseId")

{

...

But, of course that limits clicks to the specific cell in order to get its value. Is there a way to get that value on a click on any cell in the row?

answered on 17 Nov 2011, 10:52 AM

RadGridView-SL4-AR-17.zip

Hi Rob Ainscough,

I created a small project illustrating the idea from this example. Still, the event is fired correctly for RadGridView in the RowDetails as well. Does this scenario correspond to yours ? Can you reproduce the same behavior on the attached project ?

Greetings,
Maya
the Telerik team

Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>

answered on 15 Aug 2012, 05:56 PM

Hi Maya,

Problem with RowActivated is that if the row is already activated, then no event fires, so then we have to add code to deal with that situation. For many of us that buy/subscribe to 3rd party tools is so that our work load is reduced. I share Chris's frustration, but I also realize there is not much point in doing more work (by Telerik) on a technology that has ended it's life and the new "fad" is HTML5.

SL5 is better (solves more end user problems) than HTML5 but neither are as good as Windows Forms in terms of ease of application development and ROI. The biggest problem with SL5 is that much of it doesn't have adequate documenation (including you folks on your products). Why I mention this on a "DoubleClick" event is because there are developers such as myself that don't have the time and we expect 3rd party tools to save us time, not increase our time. In fact, the entire point of 3rd party tools is to save time and accomplish tasks that we would have to code ourselves. Rather than a company hirings a programmer to do exclusive UI work we buy 3rd party tools, such as Telerik ... it's much more cost effective.

Sooo, when we see what we consider basic features missing and have to keep coding work arounds or adding more complex code to deal with a situation we feel we paid for in a 3rd party tool, it gets frustrating.

I'd even venture to guess that the smaller the company the more likely they'll look at 3rd party tools ... and those tools need to help us get things done faster. And lets face it, when it comes to code bloat SL is certainly a top 10 for excessive code. But there again, many products from Microsoft seem to be focused on endless layers of abstraction, to the point where it's so difficult to manage the abstraction where one small change can cause massive application wide bugs ... I diverge ... but I've been around for a while (30+ years) and today's application development seems to be more a game of who can abstract the most and get less actual work done. Technologies change so frequently that all the effort that's gone into re-use and abstraction is nullified (wasted even) ... just like SL ending.

Anyway, I realize it's unlikely we'll see a RowDoubleClick, but I can appreciate the need for one.

Rob

answered on 15 Aug 2012, 06:35 PM

Hello Rob/Chris and everyone else who is ranting...

Here's how I send the double click to my view model (using MVVM Light).

This works on an already selected row/column mentioned in a previous post and it's easy to implement.

public ViewDashboard()

{

InitializeComponent();

this.radgridview1.AddHandler(GridViewCellBase.CellDoubleClickEvent, new EventHandler<RadRoutedEventArgs>(OnCellDoubleClick), true);

}

private void OnCellDoubleClick(object sender, RadRoutedEventArgs e)

{

if (e.OriginalSource.GetType() == typeof(GridViewCell))

{

AppMessages.GridDoubleClickEvent.send(e);

}

It's not a workaround, it is using the tools that have been given.

If you are driving a car and your sat nav sends you the wrong way, you have a choice.

1. Find another way or
2. Sit in the car, bash the steering wheel, kick the dog and and scream at passers by.

I choose to implement a solution and move on!

No offence intended of course, but I fail to see why a developer wouldn't implement such a simple solution.   If something better comes along then great, but since posting to this thread over a year ago I am astonished it is still going!

Here to help and happy to.

Mark.

PS: Screaming at the wife often helps!

answered on 16 Aug 2012, 01:10 AM

Hi Rob

Yes, fix the Sat Nav, but screaming at passers by releases some tension. :-)

AppMessages is part of MVVM-Light (http://mvvmlight.codeplex.com/) and allows me (and you, should you implement it) to separate code from design. Highly recommended if you are working in a team where designers are involved.

I add the handler in the constructor and when it is fired, I pass 'RadRoutedEventArgs e' to my ViewModel and check for e.ClickCount to determine if a double click was raised by the UI. You don't have to do it this way of course, you can check for e.ClickCount in your code behind and act on it as normal.

Hope that helps, but I can elaborate if you want me to.

Regards

Mark

PS: Chris.. I am not sure what you are getting at by your reply. I am not part of Telerik, just a fan, so I can't magic a solution for you apart from what has been suggested in previous posts. Happy to help though if I can.

answered on 16 Aug 2012, 06:28 AM

Hey Mark,

Think you're being a little dramatic, I'm not screaming at anyone. I've implemented a solution that works for me. I'm not in a position to set Telerik feature "priority" -- I don't have access to their customer data for feature improvements so I have no idea what is or isn't important.

Given the age of this thread, it is somewhat surprising that no such feature has been implemented, but NOT too surprising. SL is dead (in the sense it has no future upgrade path) and I'm sure Telerik are moving resources to HTML5 ... so I agree, it's unlikely we'll ever see a RowDoubleClick implementation.

I don't use MVVM, tried it, but found it too slow on the end user side, it was "pretty" on the development side, but my end users take priority. MVVM just wasn't good on ROI and didn't really provide any benefit to my end users/clients. I'm sure Mr. Martin Fowler had good intentions with MVC but my real world has demonstrated that for a truely good and fast application the designer (View side) has to get involved in the ViewModel (logic) because there are pratical performance limits. The basic premise that the user interface changes frequently really does NOT apply, in fact, most of my end users/client would MUCH RATHER the interface NOT change ... so implementing MVVM would be like building a Space Shuttle to go from your house to the grocery store ... when a simple cheap car will do :)

A good example of where MVVM would introduce a big performance hit ... suppose you define a UserControl that has a Button - Stack Panel - Image - TextBlock. You add some DependencyProperties to my UserControl to support a User access (security) ... say a User Logs in and their access rights are define by an EventType and an EventID (extracted from a database) ... make these a part of the UserControl. EventType and EventID are values used to match up with whatever the User has access to ... if the user has a record in a database with matching EventType and EventID the UserControl IsEnabled. In order to make this follow MVVM, the UserControl needs to be able to support IsEnabled (View) which is set by a return value from a web service (Model) that matches User, EventType, and EventID (ViewModel). If I have 40 instances of these UserControls on my Page then I have to make 40 individual web service calls IF I truely want to maintain MVVM ... web services are slow, just one more layer to getting data to an application (much slower than if it were possible to use SqlClient directly which you can't do in SL). Not doing the MVVM route, I could simply make ONE web service call that gathers up all the approprite data for the User for all 40 UserControls, cycle thru that data and match up each UserControl and set IsEnabled. This IS a much faster process but IS NOT MVVM.

As you know, web services are NOT fast (any time you add a layer, you slow things down) and they are Asynchronous which may seem great but more often than not other Controls need to wait for the population of one control before they can gather up the data they need which may also be waiting on by another control.

I diverge ... sorry.

Rob

answered on 16 Aug 2012, 03:38 PM

Thank you for your MVVM Rob. "make ONE web service call that gathers up all the approprite data" That's exactly what I do and I don't use MVVM. I think it's better to spend time unit testing the web services, than unit testing the view model which might not catch all the UI errors anyway. I really don't see the advantage of re-using the view model either. I'd rather just add the whole control as a link or in a class library. I don't really care about the performance hit, MVVM is just extra code and extra files.

As for Silverlight being dead and them not putting priority on it. Even if that was the case, the controls and development are almost the same for WPF, and the windows 8 RT Metro or whatever you call it now. Siliverlight is to be supported until 2021 or 2022 at least. For me it's easier to install Silverlight than WPF business applications that can't be HTML. Maybe I should make them all WPF since I always use Out of Browser mode, but I think the install/updates are just easier with Silverlight (I could be wrong).

answered on 16 Aug 2012, 04:00 PM

Same here, I run OOB as it has SO many advantages from elevated trust (almost full access to local storage not just restricted to the My Folders) to a faster UI ... but OOB's key is that it REMOVES THE BROWSER. This is HUGE step forward for our support department ... NOT having to deal with all the browser variances and settings that can and do cause issues with non-OOB SL. Too bad Microsoft terminated SL developement, it was just starting to mature as a product and become very useful for business applications.

Anyway, maybe Microsoft will see the light ... who knows, maybe it'll come back as GoldRays v1.0 ;)

HTML5 is a step backwards in terms of what it can do compared to SL5 ... but HTML5 lives in the "sandbox" and that's all Microsoft seem to care about. I guess the dream of having "grown-up" enterprise applications running on any OS and not in a browser is still just that ... a dream :(. It does boggle my mind that in this day and age we still can't do this because of fear. It's probably what 99.9% of enterprise developers want, yet we're stuck with kiddy sandbox applications and HTML5.

Rob.

answered on 31 Jul 2013, 01:11 PM

<UserControl x:Class="MyProject.View.SilverlightControl1"

xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

xmlns:d="http://schemas.microsoft.com/expression/blend/2008"

xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"

xmlns:i="http://schemas.microsoft.com/expression/2010/interactivity"

xmlns:telerik="http://schemas.telerik.com/2008/xaml/presentation"

mc:Ignorable="d"

d:DesignHeight="400" d:DesignWidth="600">

<Grid x:Name="LayoutRoot" Background="White">

<telerik:RadGridView ItemsSource="{Binding MyItems}">

<i:Interaction.Triggers>

<i:EventTrigger EventName="RowActivated">

<i:InvokeCommandAction Command="{Binding OpenItemCommand}"/>

</i:EventTrigger>

</i:Interaction.Triggers>

</telerik:RadGridView>

</Grid>

</UserControl>


namespace MyProject.ViewModel
{


public

class MyItems : ObservableCollection<MyItem>

{

// .....

}

public class MyItem : ViewModelBase

{

// .....

public RelayCommand OpenItemCommand

{

get

{

return new RelayCommand(OpenItemCommandExecute);

}

public void OpenItemCommandExecute()

{

// to do anything

}

}

....