[fpc-devel] LCL accessibility inconsistencies
Hi, I'm not sure whether I'm right here, if not, so please apologize my question! I think I detected an error in the LCL accessibility implementation - at least the TControl.AccessibleRole has inconsistencies so a screenreader software doesn't work correctly. How can I get contact with the responsible developers to solve this problem? Thanks, Frank ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] LCL accessibility inconsistencies
On 14 Oct 14, at 18:48, Frank wrote: Hi, I'm not sure whether I'm right here, if not, so please apologize my question! I think I detected an error in the LCL accessibility implementation - at least the TControl.AccessibleRole has inconsistencies so a screenreader software doesn't work correctly. How can I get contact with the responsible developers to solve this problem? Lazarus has its own mailing lists (see http://lists.lazarus.freepascal.org/mailman/listinfo). There is also the WWW based forum (http://forum.lazarus.freepascal.org). Obviously, if you found a bug in LCL, you should be able to file a bug report for project Lazarus in the bug repository available on http://bugs.freepascal.org. Tomas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] suggestion: virtual method co-variance
Isn't that exactly what is done in C++? It is prepared in library code. On 10/14/2014 12:40 PM, Marco van de Voort wrote: I recently had to dive a bit into C++ again, and reconnected with a feature I liked at first sight, the C++ covariance of virtual methods (changing the return type of a overriden method to a descendant of the original type). Googling a bit it seems that some languages(C#) also seem to allow this for parameters. (not just return types) I suddenly wondered why it was never proposed or talked about for FPC, since it seems such a nice feature. Is there something particularly wrong with it? To a certain degree it can be emulated with generics, but that it requires a generic for every type, and must be prepared in the library code. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] Invalid line-info on array of const
On 09/04/2014 10:36 PM, Florian Klämpfl wrote: Am 04.09.2014 um 21:52 schrieb Joost van der Sluis: I can add this check to the debugger anyway, but am I right that the line info in the example is wrong? Then I can try to fix it. Yes, it is wrong. Go ahead and fix it :) Done. (r28824) The hesitated to write the line-number of the start of the current function in this case, but a remark in the dwarf-specification suggest to use 0 as line number in cases like these, so I used that. But gdb choked on it. Probably because with this change line-information is generated for instructions that do not correspond to the start of a statement/line. In that case IsStatement has to be set to false, so I added that too. Regards, Joost. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
