Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2008-05

Interesting things with latest snapshot of lazarus 9.25

8 messages · 5 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

matt shaffer

First off, I'd just like to say WOW it's taking absolutely forever for the next version of lazarus. It didn't take this long from 9.23-9.24; but then again it brought some problems like transparency with it. Ok first thing: When compiling, it always gives tons of errors about how it was unable to test variables blah blah blah.. and secondly, if there's a lot of timage components, my app dies. *sigh* Hope lazarus development speeds up.. I really need image transparency.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.lazarus.freepascal.org/pipermail/lazarus/attachments/20080526/1f28d1c6/attachment.html

Reply by email

Vincent Snijders
to matt shaffer
matt shaffer wrote
First off, I'd just like to say WOW it's taking absolutely forever for the next version of lazarus. It didn't take this long from 9.23-9.24;

For our next release we want to use fpc 2.2.2, so until then no new Lazarus release. Which doesn't mean nothing is happening, see
http://svn.freepascal.org/cgi-bin/viewvc.cgi/lazarus-all.log?view=markup&root=logs

Show quoted text 5 lines
but then again it brought some problems like transparency with it. Ok first thing: When compiling, it always gives tons of errors about how it was unable to test variables blah blah blah.. and secondly, if there's a lot of timage components, my app dies. *sigh* Hope lazarus development speeds up.. I really need image transparency.

Thanks for testing the snapshots, that is what they are for. It would be helpful, you created test application that show the problems you are having with the snapshpt

If you want to help, create test applications that show the problems you are having with the snapshots, and create bug reports for each of them. See http://wiki.lazarus.freepascal.org/How_do_I_create_a_bug_report

Vincent

Reply by email

matt shaffer
to Vincent Snijders

Ah yeah I was going to submit one for the transparency problem for 9.24 a while back, but it was already reported. I didn't know I could submit a bugtracker for the snapshots though, so that's good to know. Also I have encountered an interesting problem; lnet (latest) + lazarus 9.24 and 9.25 can cause some very odd problems... such as the timage component disappearing. Now; how am I supposed to report that? It could be lnet's creator's fault.. =/

Vincent Snijders wrote 32 lines
matt shaffer schreef: > First off, I'd just like to say WOW it's taking absolutely forever for > the next version of lazarus. It didn't take this long from 9.23-9.24; For our next release we want to use fpc 2.2.2, so until then no new Lazarus release. Which doesn't mean nothing is happening, see http://svn.freepascal.org/cgi-bin/viewvc.cgi/lazarus-all.log?view=markup&root=logs > but then again it brought some problems like transparency with it. Ok > first thing: When compiling, it always gives tons of errors about how it > was unable to test variables blah blah blah.. and secondly, if there's a > lot of timage components, my app dies. *sigh* Hope lazarus development > speeds up.. I really need image transparency. Thanks for testing the snapshots, that is what they are for. It would be helpful, you created test application that show the problems you are having with the snapshpt If you want to help, create test applications that show the problems you are having with the snapshots, and create bug reports for each of them. See http://wiki.lazarus.freepascal.org/How_do_I_create_a_bug_report Vincent _______________________________________________ Lazarus mailing list http://www.lazarus.freepascal.org/mailman/listinfo/lazarus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.lazarus.freepascal.org/pipermail/lazarus/attachments/20080527/c27a720e/attachment.html

Reply by email

Felipe Monteiro de Carvalho
to matt shaffer: First off, I'd just like to say WOW it's taking absolutely forever for the next version…

2008/5/26 matt shaffer :

First off, I'd just like to say WOW it's taking absolutely forever for the next version of lazarus.

wow is what I would use to describe the new features which we are preparing for the next release, like full windows unicode support, much better wince support with unicode, dozens of fixes in gtk2, TIcon properly implemented, etc.

*sigh* Hope lazarus development speeds up.. I really need image transparency.

Lazarus is free software. If you are not happy with the current development you can submit a patch or pay someone to submit a patch. Everything else is just a courtesy.

Having said that we have a policy of no regressions. So if any regression is present, then the next release won't be released until all regressions are fixed, so one release can't work worse the the last.

By submiting bug reports we can know which regressions were introduced so they can be scheduled to be fixed before the next release.

Felipe Monteiro de Carvalho

Reply by email

matt shaffer
to Felipe Monteiro de Carvalho: 2008/5/26 matt shaffer : wow is what I would use to describe the new features which we are

Oh the ticon thing (and also the systray icon) were also on my top list of things I wanted fixed in lazarus. I realize that it is free software, and I use snapshots because they have the transparency fixed and I happened to come across those errors in the snapshot. I do wonder though, you say that the newest version is no worse off than the last version; I do mostly agree with you on that, but things apparently do slip through the cracks - like the transparency glitch in 9.24. Yes, I really do appreciate you and everyone else's work on the lazarus project; it's something I'm not capable of really working on, so instead I just use it. I don't know the inner workings of lazarus, or why too many timages would crash it, so I cannot help much (by providing a patch, for example.) I'm still not even sure if that IS the cause; but it seems to be. If it truly is a bug, which I will determine by creating a completely fresh application and filling it with a minimum of 60 timages, then I will submit a Tue, May 27, 2008 at 5:54 AM, Felipe Monteiro de Carvalho <

Show quoted text 34 lines
wrote: 2008/5/26 matt shaffer : > First off, I'd just like to say WOW it's taking absolutely forever for the > next version of lazarus. wow is what I would use to describe the new features which we are preparing for the next release, like full windows unicode support, much better wince support with unicode, dozens of fixes in gtk2, TIcon properly implemented, etc. > *sigh* Hope lazarus development speeds up.. >I really need image transparency. Lazarus is free software. If you are not happy with the current development you can submit a patch or pay someone to submit a patch. Everything else is just a courtesy. Having said that we have a policy of no regressions. So if any regression is present, then the next release won't be released until all regressions are fixed, so one release can't work worse the the last. By submiting bug reports we can know which regressions were introduced so they can be scheduled to be fixed before the next release. -- Felipe Monteiro de Carvalho _______________________________________________ Lazarus mailing list http://www.lazarus.freepascal.org/mailman/listinfo/lazarus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.lazarus.freepascal.org/pipermail/lazarus/attachments/20080527/2a9aa0ca/attachment-0001.html

Reply by email

Felipe Monteiro de Carvalho
to Joao Morais: Nice point. I have some wrappers to have abstract access to a graphic framework. Is there…
Joao Morais wrote
Nice point. I have some wrappers to have abstract access to a graphic framework. Is there a way to know if I am using a widgetset that expect an utf string instead an ansi one?

Only gtk1 still uses ansi, because gtk1 doesn't suppport unicode. If you don't need to support gtk1, then you can suppose unicode works everywhere. All new widgetsets are built with unicode support from the beginning.

Felipe Monteiro de Carvalho

Reply by email