2. It's working at my side, at least partially(Win7/Laz trunk/FPC 3.0.0). Sometimes I can change the values sometimes not.Wow! yes. I've double checked, and it also working, not for all cases.
PS: If needed I can create a more polished version and add it to the bug tracker.Sure, please do that. And let us know the issue number here.
Wow! yes. I've double checked, and it also working, not for all cases.I guess you can consider 2 solved too, or if you like you can extend the typekind, just make sure it doesn't introduce regression.
@x2nieNo it isn't solved yet. I only show the original code. But I am trying the point (2). 8)QuoteWow! yes. I've double checked, and it also working, not for all cases.I guess you can consider 2 solved too,
or if you like you can extend the typekind, just make sure it doesn't introduce regression.Excuse me, what is "regression"? is that related to cross platform issue?
Excuse me, what is "regression"? is that related to cross platform issue?I mean when you solve an existing bug or extend a feature, but in the same time you introduce another bug. Since lazarus is a complex project, it happens very often.
I've reported this as issue #0029503You should create a patch, if you're under windows, just download Tortoise SVN, then click Create Patch on the menu, after you finish editing the source. It's much easier for developer to apply the patch.
@x2nieAbove procedure.
Yes, sure! Just tell me which line has changed exactly.
... then click Create Patch on the menu, after you finish editing the source. ...Well, I tried. Not so bad! (I've sent the patch) :D
It's much easier for developer to apply the patch.
Just copy-pasting a block of code can easily overwrite some other recent change.
.. people making patches with weird and complicated ways, like making changes to a release version sources and using an external diff tool to compare them
Well, I tried. Not so bad! (I've sent the patch) :D
Thanks you GetMem. It was easiest way to create patch.
I have been has trouble to remember the steps of creating patch, yours is easy to do easy to remember.
Wow it was me! I mean, I am working alone and always using non-diff tool (WinMerge) to compare. :-[
I really hope that someday, just using Lazarus I can create a patch!
Nowadays: Lazarus -> Help -> Report a Bug is useless menu item. 8)
you know, Lazarus has real DIFF tool inside, but no menu to activate it unless the files in editor is edited outside Lazarus by accident .
Did you earlier copy files around and used an external diff tool?Yes as always.
It is explained in every SVN tutorial. It is explained in Lazarus wiki. The "Create Patch" in TortoiseSVN does not even need an explanation because it is so obvious.If "a person" was me, it because..., for honest, I don't know what shall I do with *.patch. see?
So, how can it be difficult for a person who is able to fix bugs in a > 2000000 LOC SW project?
It has always puzzled me that some people who a capable of making valid changes to a huge Lazarus code base, find it too difficult to run "svn diff" command or to click "Create Patch".Hey, let your puzzle being answered with this caricature (not a joke, but it funny):
Actually I don't see how it would happen technically. It would inevitably require some clumsy and error-prone copy-pasting, wouldn't it?wrong. >:D it would be very good and easy.
It is especially dangerous in Lazarus Tools menu because people would create patches from the release version.
No good!
But hey, why would you use Lazarus to create a patch?No, not you, it should I am who say to you, "Why you turn this simple process into more complicated?" ! O:-)
TortoiseSVN allows to create it with a single "Create Patch" click. How could Lazarus make it any simpler?
The whole patch concept logically belongs to the domain of revision control tools. Why do you want to turn this simple process into a more complicated process?
I know git. But still don't want any patch. I usually only "pull request" github.
patch is not that intuitive for my eye.
Hey, let your puzzle being answered with this caricature (not a joke, but it funny):
wrong. >:D it would be very good and easy.
1) It should be able to run with svn/git source-coded Lazarus.
2) Current lazarus build/compiling is already able to detect whether svn available.
So if it release version (no svn nor git), just hide the menu. Otherwise the "Create Patch" menu visible.
I know git. But still don't want any patch. I usually only "pull request" github.
patch is not that intuitive for my eye.
Actually GitHub's "pull request" and a patch file are conceptually the same thing.
With r51422 the circle is complete. Thanks @Juha, @Ondrej!
@valdir.marcosProbably not, it's high chance for regression. Though it would be nice, if at least the Ctrl + Click feature would make it to Lazarus 1.6. @Juha what do you think?
Is there available time to all these changes still be merged into Lazarus 1.6.0?
4. #29510Thank you GetMem. That would be great!
@x2nieYou're welcome! I hope you feel better soon.
Thank you GetMem. That would be great!
I am sick today. Cold flu. I cant check the code now.
4. Object Inspector should able to remember the last selected property (for next selected control).
OI should select "Text" property in the end of any below activities:
a) Drop a TEdit in form, change the Text property, drop a TButton, select again the TEdit
b) Drop a TEdit in form, change the Text property, drop a TEdit
(lazarus: none property is selected, it should be "Text" property is selected.)
Have all these Lazarus's missing Delphi features been implemented?It was more then two years ago, but IIRC yes.