I need to group by one field and summarize (weighted average), then group by another field and summarize (weighted average with non-associative weight).
The issue is, in T-SQL parlance, SummaryFields are exactly like window functions. You can partition by (group with RunningBand) and order by (only works with running sum so far), but here's the issue: the output of the window function is repeated once for every row. It's not like a group where the output is once per group.
Summary fields can add window function calculations to a data table but they cannot invent a new data table with fewer rows, one for each group.
Lemme give an example. This is the data table:
A, 1
A, 2
B, 3
B, 4
B, 5
A, 1
A, 2
B, 3
B, 4
B, 5
Say I want to group by the first column and average the second column, then I want to group everything and average that. I want to do this:
A, 1.5
B, 4
Then the second level average on 1.5 and 4 gives 2.75.
A, 1.5
B, 4
Then the second level average on 1.5 and 4 gives 2.75.
Then when I average 1.5, 1.5, 4, 4, and 4, I get 3 instead of 2.75.
I need some way to skip the second and third A and B rows.
So the question is, do I hack around this or do I try to make grouping (rather than partitioning) a thing?
It would not be via summary fields since by their very nature they must be window functions.
It would not be via summary fields since by their very nature they must be window functions.
Unless... I renamed RunningBand PartitionByBand and introduced a GroupByBand that did magic.
Let's define the magic. if a GroupByBand is set, the summary field only operates on a group of rows rather than single rows. The easiest is to say the first or last row. Assuming you're only summarizing summary fields which partition by that group or a higher group, it does not matter which row is used since they will be identical.
Otherwise, you'll have to figure out how to summarize the rows into a group. Which could actually be done if the Expression became a child collection type expression.
Hmm.
I did call that out explicitly here: https://github.com/jnm2/DevExpressMods/blob/master/Readme.md#getting-started
But I do need to reword that now that there is a NuGet package.
But I do need to reword that now that there is a NuGet package.
SummaryFieldsFeature.Apply should probably be the preferred way to do it, rather than ModdedEndUserDesigner.cs.
Thanks for the tip!
Ah, I didn't catch that then
Our specific situation was a bit different because we create the
XRDesignForm with code
Back before I realized
IDesignForm gave access to the MDI controller and the dock manager, Apply was more complicated and I thought adding a sample modded designer would be helpful. But I think it's probably more harmful than anything. It ended up helping to introduce a bug (#9).
Just need to finish #8.
I guess it's also hard to use for some people because they're not yet up-to-date with DX16.1
And learn enough NuGet-foo to put them all in a package and restore the correct binaries. If that's even possible. If not, one NuGet package per DevExpress version.
Also, there were breaking changes between 15.1 and 15.2 so I'd need to start using compiler preprocessing.
Long story short- if someone actually needs this, I'll do it. If not, I'll work on something more useful.
Binding redirects don't solve the breaking API changes issue.
Does this room still avaliable ?
I use XAF framework to developing my production but I still have something to know with XAF framework.
@siwaphatpg_twitter Sorry, it's not. The best thing I can recommend is https://www.devexpress.com/support/.
This Gitter chat is only about the project described by this readme: https://github.com/jnm2/DevExpressMods#end-of-an-era
This Gitter chat is only about the project described by this readme: https://github.com/jnm2/DevExpressMods#end-of-an-era
hello..friends...
how can i get the mouse click a tabFormControl1 object
..Double click on the blank area
thankyou
i need your help
any help is welcome Thanks very much...
PS. excuse my English...i only know a little English....
this.tabFormControl1.MouseDown += F_MouseDown;
//here the click... it can click the pagetab..
//i don't want it click the tabtitle
if (e.X == 8 && e.Y == 9)
{
//click the tabtitle right : on the blank area
//i can do something
// such as i can change the form :
this.WindowState = FormWindowState.Maximized;
}
else
{
//is click the tab title... ...can do something
}
@AtlantisDe This chat room is for a specific extension to the DevExpress report designer. If you need help with anything more general, this place will get you the help you need: https://www.devexpress.com/Support/Center/
@itprodavets Hey, sorry... I have to point you to https://www.devexpress.com/Support/Center/ to find an answer for that. This chat room is for a modification to the DevExpress report designer, not for DevExpress products themselves.