17 replies to this topic

[Thomas Steinmaurer]

Hello,

I have a problem with NextDBGrid that is related to scrolling in the dataset. It seems to be a painting issue.

* After opening the result set, I have something like shown in  Clip1.jpg   68.49KB   12 downloads.
* Then I use the Page-Down key several times. I do get something like in  Clip2.jpg   69.4KB   12 downloads. See the gap between 53 and 90, although there are records between these numbers.
* Then I navigate to a previous record with a mouse-click. The selected record gets redrawn and thus shows the proper data.  Clip3.jpg   69.02KB   14 downloads

In general, when I switch to another application and then back to my application, thus if a repaint gets enforced, the currently displayed data is shown correctly, until the next scroll event as discussed above is issued.

I'm using D2010 Prof., NextDBGrid 5.0.5.

Thanks
Thomas

[jerz]

Hi,

I have the same proble. What is the solution?

(BSD 2006 + AnyDac 2)

--
Jerzy

[Boki (Berg)]

Hello,

I am still working on solution. Workaround is to set doBufferRecords to True in DataAwareOptions and doRetreiveRecords to True.

I hope that in following days I will find a solutions.

Best regards

[jerz]

I am still working on solution. Workaround is to set doBufferRecords to True in DataAwareOptions and doRetreiveRecords to True.

This workaround is not good, especially in large collections and remote work. Can I expect to solve this problem?

[Boki (Berg)]

Hello Jerz,

Unfortunately I didn't find a solution. I have only partial results with painting bugs while scrolling.

Maybe someone have idea how this problem may be solved, to help me. I am a little bit out of ideas for this problem.

I will continue to work on this problem. Please sorry for taking so much time.

Best regards

[RBi]

Hallo,
if you don't have a workaround, you can test this:
Insert in the procedure TNxGridDataLink.DataSetScrolled this line
....
inherited;
FGrid.Invalidate;
end;

Ralf

[jerz]

Boki,

Is Integration solution is acceptable in the long run?


Regards
j

[Boki (Berg)]

Hello jerz,

Maybe I didn't understand your question, but I will try to go arround RBi's tip.

Best regards

[jerz]

Sorry for the mistake, I wanted a solution given by the RBI's.

[Boki (Berg)]

Hi,

Solution from RBI worked fine, but there is a problem when scrolling up after successfully scrolling down.

I am working on them.

Best regards

[jerz]

Hi Boki,

are there any news on this subject?


--j

[Boki (Berg)]

Hello Jerz,

Please sorry, but I don't know the solution. I will need more time to solve it

If you want, I may refund your order

Best regards

[Thomas Steinmaurer]

Hello,

I wonder if you made any progress with that? I really like NextGrid, but IMHO NextDBGrid isn't useable, because it heavily relies on an accurate record number of the underlaying TDataset-based component, which is a NO-GO for client/server environments with largish tables.

TDBGrid is fine. TSMDBGrid from Scalabium works fine as well.

So, any new information on this issue?

Thanks,
Thomas

[Boki (Berg)]

Hello Thomas,

I am sorry, but I still don't have a solution for this problem. It is related to the core design of NextDBGrid.

NextDBGrid is not inherited from standard DBGrid and this is why this problem exists.

I am sorry again, this issue gives me a lot of frustrations, because I can't solve it I have feel bad when someone have this problem, and I offer to refund or do some other feature instead.

Best regards

[Thomas Steinmaurer]

Hmm, ok.

Thomas

[jerz]

Hi Boki.

Let me know if you solve the problem. We are happy to go back to NextDBGrid, but for now it is useless for me in Client/Server applications.

Regards
Jerzy

[Steve Faleiro]

I too am getting this issue. Does there exist any resolution at this time?

[Boki (Berg)]

Hello Steve,

Unfortunately nothing yet. This problem is related to the core design of NextDBGrid. It gives a some advantages, but as may be seen it gives a problem with this kind of DataSet's.

I am returning from time to time to this problem, but I don't know yet is can be solved.

Best regards