When I type accented letters in the IDE or in my forms, they appear duplicated: ?? ?? ?? ?? ?? ...

Searching the bugtracker, I found
this:http://bugs.freepascal.org/view.php?id=15688

It seems to be a GTK2 problem, in the CheckDeadKey procedure (lcl/interfaces/gtk2/gtk2proc.inc).

I tried to comment out such code and replace the call by a single call to gtk_im_context_filter_keypress. It solved the duplication problem but I can't type an accent key (a dead key) in one control, and after type the letter in other control. It's not a big problem to me, but it's a pattern in applications behavior.

Does anybody know how can I contact someone in the development team and talk about this? I'd like to help to improve the GTK2 support, but I'm a newbie about this...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130707/dc021fdc/attachment.html>

Looking at the bug thread it seems that there is no solution yet that works on all systems, right?

Mattias

Hello, Mattias! I don't know... I have no problems with native win32 widgetset. Did anybody test GTK2 widgetset in Windows? Maybe I should do it, just to see its behavior, although I won't neet it.

Done, I have just tested GTK2 in Windows (XP). The letter duplication doesn't happen. If I type an accent (a dead key) in one control, and move the focus to other control, the first "loses" the accent. It's a good behavior (to me). I made the change in gtk2proc.inc and the behavior remains the same.

In Linux, with the original gtk2proc.inc, I have the letter duplication problem. Changing the gtk2 binding code, I can type accents fine. But, if I type a dead key in one control and move to other, the accent "stays" in the first control, waiting for the letter. I don't see it as a big problem.

The changes I made:
- Remove the CheckDeadKey procedure
- Replace its call by a: *gtk_im_context_filter_keypress(im_context, AEvent);**
*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130707/b9c134cc/attachment.html>

[...]

>> Looking at the bug thread it seems that there is no solution yet that >> works on all systems, right?

[...]

I meant:
It seems for some people the accented characters do work on their gtk2 system, for others it does not work. If you change it, it might break on other systems. Maybe it depends on gtk2 version, keyboard and window manager.
You have to test it on various gtk2 systems or ask people with other systems to test.

Mattias

Should TObject or TComponent have a Comment property?

I think they should. One for the design itself and one for describing the usage at design or runtime.

Smalltalk has it.

Consider it a version of the Hint property but for the developer

vfclists . wrote

Consider it a version of the Hint property but for the developer

That's the job of documentation. Fix the documentation in Lazarus IDE (format, content, integration), and your problems is solved.

Regards,
G.

Annotations like in Java would be nice...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130712/baacaa00/attachment.html>

Annotations like in Java would be nice...

No IMHO, that would complicate reading the code (more cluttered) as you can see in the newer Delphi versions (called attributes instead of annotations though).

Hello, guys.
I've just found that the duplicated accents problem in GTK2 only occurs when I configure my system language to Brazilian Portuguese. The problem happens with any keyboard layout, just like the Brazilian layout and even with the US International. Any ideas?
Thanks
?derson C?ssio - Brazil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130711/d738e525/attachment.html>

This attitude which exists in the Pascal community needs to end. I say Pascal not FreePascal because when I examine a lot of free Delphi libraries I see the same thing. Lots and lots of code and not a comment in sight. It makes stuff needlessly difficult. The simple fact is documentation is never going to happen because no one has time to create it with separate tools, not even the people writing the code themselves. Coding time is the best time for documentation because that is when the intent of the code is clear and fresh in the developers mind, and incurs minimal additional cost. After all it takes barely a minute or two to describe a function, and the same parsing tools compiling the code can pull out the comments and create documentation stubs if there is a need to flesh them out further, eg with examples etc

Even a lot of the funded open source libraries don't have the resources to create proper documentation. If you take Delphi for instance, since Turbo Pascal, Delphi 7 etc the quality of documentation has gone down and these are companies that are well funded.

Instead of doing the simple thing a purist attitude has been adopted which never does anyone any good.

It is time developers learn to treat other developers as consumers not people who are supposed to RTFC or RTFM. Developers are people who are supposed to put parts together just by examining the function parameters and the function descriptions rather than wade through loads of procedure definitions and sample code full of similar sounding and confusing names.

Enough digression - if considered carefully a comment about the purpose of an object belongs in the object definition itself. Why should interrogation about an object's purpose be handled by a whole subsystem of code which has precisely nothing to do with the object, ie the operating system, a help displaying program, a filename which is the help document, as well as a search string which is the object's name? Multiply that by the variety of help displaying programs for each operating system, then by the number of operating systems available then you can see how ridiculous the whole concept is. Just bureaucracy piled on bureaucracy and attachment to ill thought out convention and tradition. There is never a direct link between an object and the help display programs available on the operating system.

There is a totally insane disconnect here. The Smalltalk guys got it right.

There can be an options to strip the comments out in the final deliverable just like the debugging information.

This is what folding editors exist for. The developer can fold them out of view when he doesn't need to read them This facility already exists in the Lazarus editor.

Any way I thinking of simple one liners, not whole paragraphs.

vfclists . wrote

Should TObject or TComponent have a Comment property? I think they should. One for the design itself and one for describing the usage at design or runtime.

No.
It takes memory and needs management. Putting this in a basic class such as TComponent is not an option. Your suggestion to 'not store it in the final executable' is not even remotely possible.

You can put a comment in front of the object or any of its properties, and the lazarus IDE will display this comment for you.

It does not take memory, and performs the same function. The only reason the smalltalk people didn't take that approach, I suppose, is because they don't have an intelligent IDE.

Michael.

as you can see in the newer Delphi versions (called attributes instead

of annotations though).

Well, then they need to be added for Delphi compatiblity :o

Benito van der Zander wrote

> as you can see in the newer Delphi versions (called attributes instead of annotations though). Well, then they need to be added for Delphi compatiblity :o

They have been added. It's just not yet in trunk.

Michael.

other than thoughts about your thread hijacking attempt? nope... no ideas at all... perhaps you meant to post this another thread specific to your keyboard problem topic? perhaps you meant to start a new thread? ;) ;) ;)

I wrote on this thread because I'd like to help to improve Lazarus code as I find problems with it.

It was a problem for which I could produce a solution in the LCL code, but Mattias Gaertner said me the problem doesn't occur on all systems. Well, I found one situation when the problem occurs, on my system.?

It's not only a "my system" problem, it's a problem in the way the GTK2 Lazarus widgetset interacts with some systems (including mine). I say that because other GTK2 applications have a normal behavior, even Lazarus applications when my system language is "English". Maybe an "if" would solve the problem; I just want to keep talking to someone who can guide me in the LCL changes without causing disasters. Mattias gave me an advice (thanks!), and I have found a new direction.?

________________________________
De: waldo kitty
Para:
Enviadas: Sexta-feira, 12 de Julho de 2013 10:38
Assunto: Re: [Lazarus] Accents in IDE and my apps

other than thoughts about your thread hijacking attempt? nope... no ideas at all... perhaps you meant to post this another thread specific to your keyboard problem topic? perhaps you meant to start a new thread? ;) ;) ;)

?derson C?ssio wrote

I wrote on this thread because I'd like to help to improve Lazarus code as I find problems with it.

i understand that but your addition has nothing to do with comment properties in TObject or TComponent :/

the only reason i saw your portion was because i have not marked this thread as "ignore" or "all caught up"... many others will not see your posts because of this...

I am new to this list, the only way I know to use it is sending a message to "". How do I know what
thread the message is going to, who is reading, who is not reading...?

I wrote on this thread because I'd like to help to improve Lazarus code as I find problems with it.

Waldo meant:
Use the 'Reply' button of your mailer, when you want to reply to someone's mail. Otherwise use the 'New' button. The reason is that the 'Reply' button copies the hidden message ID. It does not matter if you change the subject. The mail is associated with the old mail thread "Should TObject or TComponent have a Comment property".

Mattias

[...] It was a problem for which I could produce a solution in the LCL code, but Mattias Gaertner said me the problem doesn't occur on all systems. Well, I found one situation when the problem occurs, on my system.? It's not only a "my system" problem, it's a problem in the way the GTK2 Lazarus widgetset interacts with some systems (including mine). I say that because other GTK2 applications have a normal behavior, even Lazarus applications when my system language is "English". Maybe an "if" would solve the problem; I just want to keep talking to someone who can guide me in the LCL changes without causing disasters. Mattias gave me an advice (thanks!), and I have found a new direction.?

It is possible to add the changes via an IFDEF. For example:

{$IfDef EnableGtk2AccentKeyMod2}
// new solution ...
{$Else}
// old solution ...
{$EndIf}

Then you can ask people to test this by adding a
-dEnableGtk2AccentKeyMod2 to their IDE options.

Can you create a patch for this?

Mattias

thank you, mattias... i need to work on my communication method i guess ;)

The reason is that the 'Reply' button copies the hidden message ID. It does not matter if you change the subject. The mail is associated with the old mail thread "Should TObject or TComponent have a Comment property".

exactly...

the problem is that you hit the REPLY button on a post in this thread instead of hitting the NEW MESSAGE or WRITE MESSAGE button depending on your interface... REPLY is to reply to an existing thread and generally quotes the message you are replying to...

NEW or WRITE starts your own new thread... one can have many new threads as well as participating in many existing ones... just pay attention to the button you click to start your post...

i apologize that i did not make this clear in the beginning...

lastly, i should say welcome to the list! hopefully you will find it educational, enjoyable and possibly even entertaining ;)

It is such a pity that we can not induce an electric shock remotely, to each person that does that. It is so annoying! One more reason I prefer newsgroups (NNTP). The news client automatically inserts the "To" field when you press "New message".

Regards,
G.

Well, then they need to be added for Delphi compatiblity :o

I can't say anything anymore when the reason is this :)

They have been added. It's just not yet in trunk.

Hoo... a hidden branch?

It's not hidden. I suspect it is called "joost"

Michael.

Mattias, thanks for your help.
I don't know how I can create a patch... everything I know is that I must download the sources from SVN, but I'm raw about these kind of task (ashamed...)
If I give some simple instructions, can you or somebody create it?

In _*lcl/interfaces/gtk2/gtk2proc.inc*_, line 2278, we have:

CheckDeadKey;

We just need to do the solution you gave (I created a new name for the directive):

{$IfDef GTK2LatinAccents}
    gtk_im_context_filter_keypress(im_context, AEvent);
{$Else}
    CheckDeadKey;
{$EndIf}

Thanks, I hope it will be useful for some people asking in the forums!

?derson

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130715/4038b532/attachment.html>

?derson C?ssio wrote

I don't know how I can create a patch... everything I know is that I must download the sources from SVN, but I'm raw about these kind of task (ashamed...)

http://wiki.lazarus.freepascal.org/Creating_A_Patch

Easy and fun.

Regards,
Juha

Ok, I'll try it later. Thanks.
PS.: easy, fun and sloooooooooooowwwwwwww :D

branches/joost/classattributes to be precise.

Regards,
Sven