Hello Eduardo,

    I didn't realize I was talking to the same guy in both threads! Sorry. 

   All they really seem to have are the demo projects under jvcl directory. I 
didn't see one for JVDBGrid and don't know off-hand what they've done to 
improve it. But that news forum is a new one on me, maybe you'll get the 
answers you need there. 

   What features are you looking for that aren't available in the original? 
I've so many versions downloaded that I usually just "roll my own" with just 
the features needed for that app.

Dave

--- On Mon, 4/27/09, ecostas1 <[email protected]> wrote:

From: ecostas1 <[email protected]>
Subject: [delphi-en] Re: Novice's problems with Jvcl
To: [email protected]
Date: Monday, April 27, 2009, 1:29 PM











    
            
            


      
      Hi, Dave.



Thanks for your insight. After the first two days I considered doing just that, 
keeping to the good old components I knew. But I considered it might be 
something really stupid I might be doing and, as such, I tried to figure it 
out. I'd like to thank Kevin as well, but I have already posted it on 
forums.talkto. net (right after I posted it here) and I think it is time to 
find alternatives because I can't afford much time to solving such small 
problems. I'll check the source code as soon as I can and, after solving the 
problems, I may post it in the forums and switch back to Jedi in order to keep 
everything in a "single" package. 



One thing that I miss in the Jedi project is what's new or different from the 
original components. Am I wrong or do I have to go through the code to find 
what is inherited and what is changed?



Thanks again for your help.



Eduardo



--- In delphi...@yahoogrou ps.com, David Smith <djsmith_1998@ ...> wrote:

>

>  When I looked at them I saw serious bugs in several components so it is not 
> surprising if you found a bug. A small number of overworked people put that 
> gigantic batch of components together plus all the documentation (check out 
> megademo.exe in jvcl\bin directory). You could report the bug to them or try 
> and fix it yourself (but good luck recompiling those confusing packages). If 
> there's a feature in that component that you just can't find anywhere else, I 
> would extract the source code, fix it, and compile it into a separate 
> component. You could email it


      

[Non-text portions of this message have been removed]

Reply via email to