Re: [Lazarus] Unicode text difference between source editor and other Edit controls on Windows
2012/4/25 Juha Manninen :
> My tests failed when I copied the file name directly to source editor.
> They succeeded when I used a FileNameEdit to select the file name.
Did you set {$codepage ..} directive?
--
cobines
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Unicode text difference between source editor and other Edit controls on Windows
On Wed, Apr 25, 2012 at 01:26, Juha Manninen wrote: > Partly related to issue > 21817: "FileUtil.CopyFile" would failed to work with Unicode Characters > filename. > http://bugs.freepascal.org/view.php?id=21817 > > My tests failed when I copied the file name directly to source editor. > They succeeded when I used a FileNameEdit to select the file name. > Why does it happen? NTFS and FAT works in a very wrong way. They have code pages for the filename. so if you are using an Arabic filename for example, you must first know if you are using code page for Arabic (and there is more then one for Arabic afaik), or does it use UTF-8 or UTF-16 afaik. > > I remember I participated in a forum discussion about a similar issue. I can > dig it out if needed. > Then it happened on Linux, too. I piece of unicode text looked different on > source editor compared to other places, including Kate editor (part of KDE). In KDE you have also Okteka that is a hex editor, what are the differences that you see there ? > > Juha > > > -- > ___ > Lazarus mailing list > Lazarus@lists.lazarus.freepascal.org > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus > -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] Unicode text difference between source editor and other Edit controls on Windows
Partly related to issue 21817: "FileUtil.CopyFile" would failed to work with Unicode Characters filename. http://bugs.freepascal.org/view.php?id=21817 My tests failed when I copied the file name directly to source editor. They succeeded when I used a FileNameEdit to select the file name. Why does it happen? I remember I participated in a forum discussion about a similar issue. I can dig it out if needed. Then it happened on Linux, too. I piece of unicode text looked different on source editor compared to other places, including Kate editor (part of KDE). Juha -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] Projects recent files is case sensitive in Windows
Hi, Some files and projects are duplicated in the recent menu. Is there any way to clean up it?. See the attachment. Best Regards Zaher Dirkey <>-- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] Keys on Save confirmation prompt not fully working
When I close a modified unit file within the Lazarus IDE I am asked whether it should be saved or not with a message window which has the following 3 buttons: Save Discard changes Abort While the [S]ave can be selected with the keyboard by pressing S (and the S is underlined to indicate this) the other two options cannot be selected with the keyboard. A bug? -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Autocomplete with procedure varibles
On 24/04/2012 16:32, Alexander Klenin wrote: On Wed, Apr 25, 2012 at 01:33, Martin wrote: 3) Simple insert it without either ( or :=. Then one can continue typing as one likes. Excellent thinking! I agree. or even better: as long as there is a dropdown, ue to other variables (different name, same start) display both (or all 3: none; (; :=). But if there would be only this var, complete the name only Only this needs to be configurable separate from the := for other variables. I think this is too rare a case to deserve a separate option. There are far too many of them already :) Just do not insert ':=' after procedure variables -- for other cases, preserve the current behaviour. What I meant is: the := is configurable. and in proc var, you do not want it to follow the config for other var. Never mind, if that is haldcoded or has an option -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Autocomplete with procedure varibles
On Wed, Apr 25, 2012 at 01:33, Martin wrote: > 3) Simple insert it without either ( or :=. Then one can continue typing as > one likes. Excellent thinking! I agree. > Only this needs to be configurable separate from the := for other variables. I think this is too rare a case to deserve a separate option. There are far too many of them already :) Just do not insert ':=' after procedure variables -- for other cases, preserve the current behaviour. -- Alexander S. Klenin -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Autocomplete with procedure varibles
On 24/04/2012 15:13, Alexander Klenin wrote:
While calling the procedure via variable is probably more frequent,
assigning to it is a valid case too.
I can suggest several alternatives:
1) Output both "myproc(params)" and "myproc:=" items in the completion dropdown
2) Choose call vs. assignment based on the key pressed to select from
the completion list:
"(" for call, ":" or "=" for assignment.
3)
Simple insert it without either ( or :=. Then one can continue typing as
one likes.
Only this needs to be configurable separate from the := for other variables.
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Autocomplete with procedure varibles
While calling the procedure via variable is probably more frequent,
assigning to it is a valid case too.
I can suggest several alternatives:
1) Output both "myproc(params)" and "myproc:=" items in the completion dropdown
2) Choose call vs. assignment based on the key pressed to select from
the completion list:
"(" for call, ":" or "=" for assignment.
--
Alexander S. Klenin
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Compiling Win 64 bit LCL only with 32 bit IDE+cross compiler
On 23-4-2012 20:15, Mattias Gaertner wrote: > This should work > > make clean CPU_TARGET=x86_64 OS_TARGET=win64 > make clean all useride > lazbuild.exe --os=win64 --cpu=x86_64 lcl\interfaces\lcl.lpk > > Of course you need to have a 64bit compiler installed properly. Thanks, Mattias, using lazbuild seems to work ok. -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Autocomplete with procedure varibles
Am 23.04.2012 22:20, schrieb Bernd: I have something like this: var some_external_func: function(foo: bar): baz; cdecl; some_external_proc: procedure(bla: blub); cdecl; and later I will assign them with pointers received with GetProcAddress() from a dynamically loaded library. There are a lot of these functions and I need to call most of them a lot of times all over my code. It all works perfectly well with only one little annoyance: Whenever I invoke the code completion when writing a function call it will complete like a "normal" variable: some_external_func := I have to backspace and remove the := manually so I can proceed with the opening bracket. From this moment on everything is ok again, with Ctrl+Schift+Space I will have a calltip hint exactly like with normal functions. The problem is only the autocompletion. Is this intentional? At least in my current case in 90% of all times when I start typing the name of a procedure variable I actually want to call it. (actually in my current project I don't even assign them all individually with := anymore either, I have factored this one assignment out to a place where I don't have to touch it anymore, so its actually 99.9%) Would it be possible to change the behavior of autocomplete for procedure variables (maybe even make it a config option with) or would this be considered as a wontfix because other uses happen more often than my special case here? Your case is not so special... the same happens e.g. when using OpenGL functions which are procedural variables as well. Regards, Sven -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] TBitBtn with Kid=bkClose and ModalResult
On 4/23/12, Hans-Peter Diettrich wrote: > Here it returns mrCancel by default. When the ModalResult of the button > is specified, this value is returned. On close with "X" the result is > always mrCancel. > > Not worth to mimic this inconsistent behaviour in the LCL, IMO. > Older Delphi code also will be fooled when mrClose is returned, which > has been introduced only after D7. Not sure what your last statement actually means: a) LCL should return mrClose if TBitBtn.Modalresult = mrClose, even if TBitBtn.Kind = bkClose b) LCL should not return mrClose, since D7 (and earlier) does not support that. ? Bart -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
