Meinrad Recheis

> I wanted to show the render fragment in the indeterminate mode, but it spins. Oops :D ok, then let's leave it like it is.

> Yeah, we would need to envelope it in one more div. If that is easy to do then I'd go for that. If you think this could break user's...

Actually, what do you guys think of just going with the render fragment and just showing in an example how to use it for showing percentage?

I see that showing percentage is a popular request. What about indeterminate state though? Currently not even a label or icon is possible because the render fragment is only visible...

For the record, the plan is a `RenderFragment` that can be used for both determinate and indeterminate progress. The nullable int parameter will hold the percentage in the determinate case.

Why not just `InputId`? The `Internal` part seems superficial. Or maybe `InputElementId`

> @henon, what do you personally think about this? I am not sure that changing ParameterState in this way is a good idea, at least I got a bad gut...

Can you provide the equivalent python snippet for comparison?

The operators were only defined for scalars, now I added overloads for arrays and it works: ```c# [TestMethod] public void IssueByXiaozhu1988() { //>>> data = np.array([10, 20, 30, 40, 50,...

Fixed in https://www.nuget.org/packages/Numpy/3.11.1.34