-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create base class for EditLink and few most used implementations #1063
Comments
If they come in new, separate units I don't see why not. My concerns in #799 were mainly about a read/write |
Well, I thought about extending/modifying VirtualTrees.EditLink.pas so that other links could inherit most of generic methods and implement just specific things |
@Fr0sT-Brutal: That sounds good, a well designed base class for editors will be helpful. |
Done. Is it really necessary to reset FStopping on exception in TStringEditLink.EndEdit? |
Sorry, I can't comment much on that, I never worked on that code after taking over the project. But it looks strange. I wonder which kind of exceptions are to be expected here? Catching untyped exceptions isn't best practice anyway, and the covered code block seems to be too large. Maybe in case I would prefer to catch expected exceptions here only. |
Thank you for the pull request, it is now merged, but without an extended code review. |
I'm a little puzzled here too... FStopping looks like mechanism to avoid reentrance but I guess the tree itself won't let it happen. |
Somewhat related to #799. Would be nice to have basic EditLink class to inherit from and few ready-to-use most used implementations (plain edit, combobox, mask edit, spin edit...).
I could do it but first I want to be sure changes will be applied
The text was updated successfully, but these errors were encountered: