Method Design Screen Issue

Radzen Blazor Studio
61

Hi @koksal.basar,

Despite my efforts I haven't been able to reproduce the lags you are experiencing. Without a reproduction I won't be able to address them. I have already spent a few weeks of development and test time on this issue but it seems the fix I am making in the dark are mostly unrelated. The last remaining option I see is to get access to an application which shows the lag. If this is not an option then I can offer you a refund of your purchase.

62

Hi @korchev one more time,

  1. I have been your customer since Radzen's time. I think that I helped develop a product as a part of the community. Please remember, that I'm not an unsatisfied customer. The expressions I use when sharing my ideas are to convey the user's experience rather than dissatisfaction and I know that you're trying to do your best. Considering all this, a refund does not seem to be an option for me. Thinking about my sincerity, please don't offer again for a refund.
  2. Of course a seamless working experience would make me happy because I have to do a project (and this is the only project that I have). But creating a good product takes time and I know all of these. 1.16.2 is good enough to work for my project for now.
  3. If direct access to my development environment makes any difference to solve this problem please send me an email and we discuss when and how.
63

Direct access to your environment would help us as we need to run at our side where we can debug. Access to the project itself (the source code and nothing else) would probably allow us to find what is causing the lags. You can be assured that we will delete everything once the issue is solved. If you agree you can share a download link of the code over email.
We just can't spend any more time blindly investigating an issue we can't reproduce.

I offered a refund since our product no longer works satisfactory for you. I don't think staying on 1.16.2 forever is a viable solution though and would love to solve this fix once and for all.

64

I will not. Because I know you will solve the problem :slight_smile:

2 Likes
65

@korchev was too tired and had to bear with me but 1.20.6 seems to have fixed the problem.

Thanks

1 Like