Sign in Join

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

Mailing lists / lazarus / 2012-02

I made a visualization of the Lazarus SVN repository

28 messages · 9 people · –

Reply by email Subscribe to this list Your subscription

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

Bernd

...using gource. Its quite interesting and funny to watch:

http://vimeo.com/36868024

Its only a few months from last summer until yesterday but you can watch busy developers flying around from file to file, watch the customdrawn interface grow and see which developers are mostly "attracted" by which parts of the project.

Reply by email

Juha Manninen
to Bernd: ...using gource. Its quite interesting and funny to watch: http://vimeo.com/36868024 Its…

Nice.
I didn't know I was flying so much. :)

Juha

2012/2/16, Bernd :

Show quoted text 15 lines
...using gource. Its quite interesting and funny to watch: http://vimeo.com/36868024 Its only a few months from last summer until yesterday but you can watch busy developers flying around from file to file, watch the customdrawn interface grow and see which developers are mostly "attracted" by which parts of the project. -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Everton Vieira
to Bernd: ...using gource. Its quite interesting and funny to watch: http://vimeo.com/36868024 Its…

That`s so fun!

Bernd wrote 14 lines
...using gource. Its quite interesting and funny to watch: http://vimeo.com/36868024 Its only a few months from last summer until yesterday but you can watch busy developers flying around from file to file, watch the customdrawn interface grow and see which developers are mostly "attracted" by which parts of the project. -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Everton Vieira
to Everton Vieira

Look who does the things around here are a bunch of heroes. We have to increase this number. Making easy and secure is the way.

Everton Vieira wrote 19 lines
That`s so fun! Em 15/02/2012, ?s 23:17, Bernd escreveu: > ...using gource. Its quite interesting and funny to watch: > > http://vimeo.com/36868024 > > Its only a few months from last summer until yesterday but you can > watch busy developers flying around from file to file, watch the > customdrawn interface grow and see which developers are mostly > "attracted" by which parts of the project. > > -- > _______________________________________________ > Lazarus mailing list > > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Juha Manninen
to Everton Vieira

2012/2/16, Everton Vieira :

Look who does the things around here are a bunch of heroes. We have to increase this number. Making easy and secure is the way.

Everton, start providing patches. It is easy and secure! :)

Bernd, how long you think the animation is kept in the Vimeo site? It would be nice to have a similar animation from a longer period of time, saved in place where it will stay for reasonably long, and provide a link in Wiki pages.

There are amazing pieces of SW out there, like this "gource", which most people don't know about. I didn't know about it before this video.

Juha

Reply by email

Everton Vieira
to Juha Manninen
Juha Manninen wrote 5 lines
2012/2/16, Everton Vieira : > Look who does the things around here are a bunch of heroes. > We have to increase this number. Making easy and secure is the way. Everton, start providing patches. It is easy and secure! :)

Always that I can I will :) And you fly a lot brother! That`s so nice. Sure you have a very large view of it. Wish i had too.

Well, I had the idea that would be good to integrate in the IDE the process of bug report and patching. Today is too diffuse this work and many doesn't even know what it is. Make integrate in the IDE would make more concentrated and visible.

Show quoted text 18 lines
Bernd, how long you think the animation is kept in the Vimeo site? It would be nice to have a similar animation from a longer period of time, saved in place where it will stay for reasonably long, and provide a link in Wiki pages. There are amazing pieces of SW out there, like this "gource", which most people don't know about. I didn't know about it before this video. Juha -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Juha Manninen
to Everton Vieira

2012/2/17, Everton Vieira :

Show quoted text 5 lines
Em 17/02/2012, ?s 15:41, Juha Manninen escreveu: > Everton, start providing patches. It is easy and secure! :) Always that I can I will :) And you fly a lot brother! That`s so nice. Sure you have a very large view of it. Wish i had too.

I don't really have so big view. The existing code must be studied always when creating new code. A good IDE with its code browsing and other features is important then, it works as an extension of the brains.

Well, I had the idea that would be good to integrate in the IDE the process of bug report and patching. Today is too diffuse this work and many doesn't even know what it is. Make integrate in the IDE would make more concentrated and visible.

Do you have problems now creating bug reports and patches? What kind of problems?
I don't know how, and why, should patching be integrated in IDE. A patch is easy to make with "svn diff" for example. The difficult part is actually creating high quality code for a big project of over 1 000 000 LOC. There is no simple trick to make that easy.

Integrating bug reporting into IDE would have benefits if the IDE can trap an exception and include details of it in the report, together with info about the environment, and send it (semi-)automatically somewhere.
Until that is implemented, the current issue tracker works very well IMO.

Juha

Reply by email

Bernd
to Juha Manninen: 2012/2/16, Everton Vieira : Everton, start providing patches. It is easy and secure! :)…

2012/2/17 Juha Manninen :

Bernd, how long you think the animation is kept in the Vimeo site? It would be nice to have a similar animation from a longer period of time, saved in place where it will stay for reasonably long, and provide a link in Wiki pages.

I'm currently uploading an animation of the entire svn history I made tonight. I had to write a little python script to add some missing entries in the svn log when entire folders are renamed or deleted because gource can not yet deal with that correctly (it is normally best used with git). This time I made it in 960*720 pixel (HD quality) and with a nice Lazarus logo in the corner. It will be 7:43 minutes length. It is currently uploading (I have only little bandwidth) and should be available in a few hours.

It will stay at vimeo indefinitely. If you have an account at vimeo you can also download the original unaltered file (it is 120MB, h264 encoded). Maybe somebody can download the original file, add a sound track with some suitable nice and unobtrusive free music and re-upload it again.

Bernd

Reply by email

Everton Vieira
to Juha Manninen: 2012/2/17, Everton Vieira : I don't really have so big view. The existing code must be…

2012/2/17 Juha Manninen

Show quoted text 25 lines
2012/2/17, Everton Vieira : > Em 17/02/2012, ?s 15:41, Juha Manninen escreveu: >> Everton, start providing patches. It is easy and secure! :) > > Always that I can I will :) And you fly a lot brother! That`s so nice. Sure > you have a very large view of it. Wish i had too. I don't really have so big view. The existing code must be studied always when creating new code. A good IDE with its code browsing and other features is important then, it works as an extension of the brains. > Well, I had the idea that would be good to integrate in the IDE the process > of bug report and patching. Today is too diffuse this work and many doesn't > even know what it is. Make integrate in the IDE would make more concentrated > and visible. Do you have problems now creating bug reports and patches? What kind of problems?

None.

I don't know how, and why, should patching be integrated in IDE. A patch is easy to make with "svn diff" for example.

I know, but let's make visible in the IDE.

The difficult part is actually creating high quality code for a big project of over 1 000 000 LOC. There is no simple trick to make that easy.

I know too, that's why many like me are afraid of it.

Show quoted text 6 lines
Integrating bug reporting into IDE would have benefits if the IDE can trap an exception and include details of it in the report, together with info about the environment, and send it (semi-)automatically somewhere. Until that is implemented, the current issue tracker works very well IMO.

I know too, the idea is only a front end, or by start, a link in the IDE, would do.

Juha

Understand, the idea is much more about to make visible than anything else. At least by now.

Show quoted text 7 lines
-- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Everton Vieira. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120218/1d414ae7/attachment.html>

Reply by email

Everton Vieira
to Everton Vieira

2012/2/18 Everton Vieira

Show quoted text 66 lines
2012/2/17 Juha Manninen > 2012/2/17, Everton Vieira : > > Em 17/02/2012, ?s 15:41, Juha Manninen escreveu: > >> Everton, start providing patches. It is easy and secure! :) > > > > Always that I can I will :) And you fly a lot brother! That`s so nice. > Sure > > you have a very large view of it. Wish i had too. > > I don't really have so big view. The existing code must be studied > always when creating new code. A good IDE with its code browsing and > other features is important then, it works as an extension of the > brains. > > > > Well, I had the idea that would be good to integrate in the IDE the > process > > of bug report and patching. Today is too diffuse this work and many > doesn't > > even know what it is. Make integrate in the IDE would make more > concentrated > > and visible. > > Do you have problems now creating bug reports and patches? What kind > of problems? > None. > I don't know how, and why, should patching be integrated in IDE. A > patch is easy to make with "svn diff" for example. I know, but let's make visible in the IDE. > The difficult part > is actually creating high quality code for a big project of over 1 000 > 000 LOC. There is no simple trick to make that easy. > I know too, that's why many like me are afraid of it. > Integrating bug reporting into IDE would have benefits if the IDE can > trap an exception and include details of it in the report, together > with info about the environment, and send it (semi-)automatically > somewhere. > Until that is implemented, the current issue tracker works very well IMO. > I know too, the idea is only a front end, or by start, a link in the IDE, would do. > > Juha > Understand, the idea is much more about to make visible than anything else. At least by now.

And in that, could be thinking something about this movie too, it has to be more visible than is today.

Show quoted text 15 lines
> > -- > _______________________________________________ > Lazarus mailing list > > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus > -- Everton Vieira.
Everton Vieira. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120218/1f3f8c67/attachment-0001.html>

Reply by email

Juha Manninen
to Everton Vieira: 2012/2/17 Juha Manninen None. I know, but let's make visible in the IDE. I know too,…

2012/2/18, Everton Vieira :

> I don't know how, and why, should patching be integrated in IDE. A > patch is easy to make with "svn diff" for example. I know, but let's make visible in the IDE.

Thinking of it more, the patch creation could be integrated in the lazsvnpkg. Now it has "Show diff for local changes" for a single file. It could easily make a full patch of the diffs.
This is a good exercise feature for you to make. For changing the relatively small package you don't need to study the whole Lazarus internals.
First you must use the cmd line "svn diff" for your patches, later you can use a self-made GUI for it. :)
I promise to look at your patches personally if you make some.

Understand, the idea is much more about to make visible than anything else. At least by now.

The whole project needs more visibility, yes. The command used for creating patches is not very essential for it. Every developer who is able to create code for a big project is also able to run "svn diff" or a similar command.

Juha

Reply by email

Bernd
to Juha Manninen

2012/2/18 Juha Manninen :

Thinking of it more, the patch creation could be integrated in the lazsvnpkg. Now it has "Show diff for local changes" for a single file. It could

It is already integrated (I implemented this last year): Click on "commit" (because you want to commit your changes, via patch or otherwise) then the commit dialog comes up where you select the files you want to commit and then instead of the "commit" button you click on the "create patch file" button. This will create a patch file, you can preview it, edit it (remove individual hunks you don't want to include) and then save it to disk. The created patch file will include all selected changes in one file, is suitable to be attached to bug reports and to be used with the patch utility. I use this to make all my patches.

Bernd

PS: my earlier mentioned upload of the new animation was interrupted and then I also spotted an error, to fix it I need to encoe it another time, It will take a few more hours.

Reply by email

Hans-Peter Diettrich
to Juha Manninen: 2012/2/18, Everton Vieira : Thinking of it more, the patch creation could be integrated…
Thinking of it more, the patch creation could be integrated in the lazsvnpkg. Now it has "Show diff for local changes" for a single file. It could easily make a full patch of the diffs.

Just a note from my experience with patches:

My installation contains some patches, which probably never will go into the official repository. When I work on a new problem, and finally found a solution, a simple diff is not ready for submission. Instead the "new" modifications had to be extracted (how?), then tested in a clean environment, at least for completeness, before the final diff can be submitted.

This is what I (and other contributors) need support for, so that less patches are rejected only for formal reasons ("too much noise"...).

DoDi

Reply by email

Juha Manninen
to Bernd: 2012/2/18 Juha Manninen : It is already integrated (I implemented this last year): Click…

2012/2/18, Bernd :

Show quoted text 10 lines
It is already integrated (I implemented this last year): Click on "commit" (because you want to commit your changes, via patch or otherwise) then the commit dialog comes up where you select the files you want to commit and then instead of the "commit" button you click on the "create patch file" button. This will create a patch file, you can preview it, edit it (remove individual hunks you don't want to include) and then save it to disk. The created patch file will include all selected changes in one file, is suitable to be attached to bug reports and to be used with the patch utility. I use this to make all my patches.

Right! I didn't know of that. I use git + git-svn link myself. Ok, Everton, the tool is there. You can start making patches for other parts of Lazarus!

Bernd, do you maintain the package?
The patch feature works well but its GUI is little broken.
1. the ListView always shows a HourGlass cursor.
2. What are the 2 text controls up there, a Combobox and a Memo? Both are empty and have no hints or titles about their meaning. If I type something the the Combobox, I get a "List Index out of Bounds" error.
3. I got memory leaks sometimes (not always) from the "Show Log" feature. It is a good idea to use -gh always when developing.

IMO the "Patch" feature should have its own entry in the menu. "Commit" term is associated with SVN commits. I didn't understand to look for it there.

PS: my earlier mentioned upload of the new animation was interrupted and then I also spotted an error, to fix it I need to encoe it another time, It will take a few more hours.

No problem.
I am curious, how long does gource take to generate such animation? It uses some advanced auto-layout algorithm for the node placement, bloom effects and such details.
I could imagine it needs some processing power.
On the other hand, today's computers have a lot of processing power.

Juha

Reply by email

Juha Manninen
to Juha Manninen

Now the memory leak came from svnstatusform :
---

Call trace for block $00007F2CC17A4400 size 64
$00000000013502DA line 106 of svnstatusform.pas
$00000000006218CD line 1088 of include/application.inc $000000000061EDB6 line 401 of include/application.inc $0000000000622EC3 line 1282 of include/application.inc $0000000000623605 line 1414 of include/application.inc $00000000008070C6 line 255 of qt/qtobject.inc
$000000000062358A line 1402 of include/application.inc $00000000005BEDE3 line 119 of lazarus.pp
Call trace for block $00007F2CC17DF080 size 29
$00000000013502DA line 106 of svnstatusform.pas
$00000000006218CD line 1088 of include/application.inc $000000000061EDB6 line 401 of include/application.inc $0000000000622EC3 line 1282 of include/application.inc $0000000000623605 line 1414 of include/application.inc $00000000008070C6 line 255 of qt/qtobject.inc
$000000000062358A line 1402 of include/application.inc $00000000005BEDE3 line 119 of lazarus.pp
Call trace for block $00007F2CC17DF500 size 28
$00000000013502DA line 106 of svnstatusform.pas
$00000000006218CD line 1088 of include/application.inc $000000000061EDB6 line 401 of include/application.inc $0000000000622EC3 line 1282 of include/application.inc $0000000000623605 line 1414 of include/application.inc $00000000008070C6 line 255 of qt/qtobject.inc
$000000000062358A line 1402 of include/application.inc $00000000005BEDE3 line 119 of lazarus.pp
Call trace for block $00007F2CC17DED80 size 27
$00000000013502DA line 106 of svnstatusform.pas
$00000000006218CD line 1088 of include/application.inc $000000000061EDB6 line 401 of include/application.inc $0000000000622EC3 line 1282 of include/application.inc $0000000000623605 line 1414 of include/application.inc $00000000008070C6 line 255 of qt/qtobject.inc
$000000000062358A line 1402 of include/application.inc $00000000005BEDE3 line 119 of lazarus.pp
Call trace for block $00007F2CC1827B00 size 53
$00000000013502DA line 106 of svnstatusform.pas
$00000000006218CD line 1088 of include/application.inc $000000000061EDB6 line 401 of include/application.inc $0000000000622EC3 line 1282 of include/application.inc $0000000000623605 line 1414 of include/application.inc $00000000008070C6 line 255 of qt/qtobject.inc
$000000000062358A line 1402 of include/application.inc $00000000005BEDE3 line 119 of lazarus.pp
Call trace for block $00007F2CC17A3DE0 size 64
$00000000013502DA line 106 of svnstatusform.pas
$00000000006218CD line 1088 of include/application.inc $000000000061EDB6 line 401 of include/application.inc $0000000000622EC3 line 1282 of include/application.inc $0000000000623605 line 1414 of include/application.inc $00000000008070C6 line 255 of qt/qtobject.inc
$000000000062358A line 1402 of include/application.inc $00000000005BEDE3 line 119 of lazarus.pp

2012/2/18, Juha Manninen :

Show quoted text 43 lines
2012/2/18, Bernd : > It is already integrated (I implemented this last year): Click on > "commit" (because you want to commit your changes, via patch or > otherwise) then the commit dialog comes up where you select the files > you want to commit and then instead of the "commit" button you click > on the "create patch file" button. This will create a patch file, you > can preview it, edit it (remove individual hunks you don't want to > include) and then save it to disk. The created patch file will include > all selected changes in one file, is suitable to be attached to bug > reports and to be used with the patch utility. I use this to make all > my patches. Right! I didn't know of that. I use git + git-svn link myself. Ok, Everton, the tool is there. You can start making patches for other parts of Lazarus! Bernd, do you maintain the package? The patch feature works well but its GUI is little broken. 1. the ListView always shows a HourGlass cursor. 2. What are the 2 text controls up there, a Combobox and a Memo? Both are empty and have no hints or titles about their meaning. If I type something the the Combobox, I get a "List Index out of Bounds" error. 3. I got memory leaks sometimes (not always) from the "Show Log" feature. It is a good idea to use -gh always when developing. IMO the "Patch" feature should have its own entry in the menu. "Commit" term is associated with SVN commits. I didn't understand to look for it there. > PS: my earlier mentioned upload of the new animation was interrupted > and then I also spotted an error, to fix it I need to encoe it another > time, It will take a few more hours. No problem. I am curious, how long does gource take to generate such animation? It uses some advanced auto-layout algorithm for the node placement, bloom effects and such details. I could imagine it needs some processing power. On the other hand, today's computers have a lot of processing power. Juha

Reply by email

Bernd
to Juha Manninen: 2012/2/18, Bernd : Right! I didn't know of that. I use git + git-svn link myself. Ok,…

2012/2/18 Juha Manninen :

Show quoted text 9 lines
Bernd, do you maintain the package? The patch feature works well but its GUI is little broken. 1. the ListView always shows a HourGlass cursor. 2. What are the 2 text controls up there, a Combobox and a Memo? Both are empty and have no hints or titles about their meaning. If I type something the the Combobox, I get a "List Index out of Bounds" error. 3. I got memory leaks sometimes (not always) from the "Show Log" feature. It is a good idea to use -gh always when developing.

I don't maintain it, I only made a few patches for it because it seems nobody else did anything in it for a very long time and I missed some features, so I quickly implemented them myself, but you are right, it still needs much more work. Are you using the stable 0.9.30 version or svn trunk? I recently fixed some memory leaks (the original version was only hidding some forms instead of closing them, kept pointers around to some of these hidden forms to show them again, sometimes provoking crashes, parts of it were/are pretty confusing. I tried to fix some of the issues and it became a lot better but I did not have enough time to find them all)

I cannot currently look at the problem you mentioned about the combo box because my PC is currently busy doing the animation (I cannot minimize the OpenGL window now or move any window in front of it because that would cause corruption and many hours time wasted) but I promise I look at it soon.

IMO the "Patch" feature should have its own entry in the menu. "Commit" term is associated with SVN commits. I didn't understand to look for it there.

I put the patch button onto the commit form because it shares the same work flow until the very last moment when you actually decide whether to commit to the server or to a patch file. Maybe it should be mentioned in the menu item: "Commit / create patch" instead of only "Commit"

Show quoted text 5 lines
No problem. I am curious, how long does gource take to generate such animation? It uses some advanced auto-layout algorithm for the node placement, bloom effects and such details. I could imagine it needs some processing power.

Almost all processing power is used by ffmpeg for encoding the movie, this takes many hours on my rather old hardware. Gource itself is pretty fast and can generate it in real time with high frame rates.

Bernd

Reply by email

Bernd
to Juha Manninen: 2012/2/18, Bernd : Right! I didn't know of that. I use git + git-svn link myself. Ok,…

2012/2/18 Juha Manninen :

Show quoted text 5 lines
The patch feature works well but its GUI is little broken. 1. the ListView always shows a HourGlass cursor. 2. What are the 2 text controls up there, a Combobox and a Memo? Both are empty and have no hints or titles about their meaning. If I type something the the Combobox, I get a "List Index out of Bounds" error.

The text control is for entering the commit message and the combobox is for quickly selecting one of the previously entered commit messages.

Please file a separate bug for every individual problem you find (you have found at least 3 different problems already) so they won't be forgotten. I will try to fix them all one after the other and hope somebody will apply my fixes before it is too late for Version 1.0

Bernd

Reply by email

Juha Manninen
to Bernd

2012/2/18, Bernd :

The text control is for entering the commit message and the combobox is for quickly selecting one of the previously entered commit messages.

Yeah, I figured it out. In fact I become obsessed with the memory leaks and crashes and started to fix them myself. I think I got them all fixed now.
The code become much cleaner by using classes instead of records, and generics containers. Lots of ugly type-casts could be removed. See r35463 and r35469.

Please file a separate bug for every individual problem you find (you have found at least 3 different problems already) so they won't be forgotten. I will try to fix them all one after the other and hope somebody will apply my fixes before it is too late for Version 1.0

You could look at the remaining usability issues. At least the commit msg history list collects duplicate strings.
The HourGlass cursor problem seems to be a QT problem. With GTK2 it works better.

Juha

Reply by email

Sven Barth
to Juha Manninen
Juha Manninen wrote
The code become much cleaner by using classes instead of records, and generics containers. Lots of ugly type-casts could be removed. See r35463 and r35469.

Didn't you say you're not so sure anymore about using generics in Lazarus? ;P

Regards,
Sven

Reply by email

Juha Manninen
to Sven Barth

2012/2/19, Sven Barth :

Didn't you say you're not so sure anymore about using generics in Lazarus? ;P

Well yes I did. :-)
In this case however it made a big difference for the code clarity. Please may use them also in future but only when the benefits outweight the memory and performance penalties that were discussed earlier.

I still believe someone (you maybe) will optimize generics in FPC in future and the issue mostly goes away.

Juha

Reply by email

Sven Barth
to Juha Manninen
Juha Manninen wrote 9 lines
2012/2/19, Sven Barth: > Didn't you say you're not so sure anymore about using generics in > Lazarus? ;P Well yes I did. :-) In this case however it made a big difference for the code clarity. Please look at r35469. I may use them also in future but only when the benefits outweight the memory and performance penalties that were discussed earlier.

I already looked at your changes before writing the mail. I just wanted to tease you a little bit :)

I still believe someone (you maybe) will optimize generics in FPC in future and the issue mostly goes away.

Thank you for your confidence :)

Regards,
Sven

Reply by email

zeljko
to Juha Manninen: 2012/2/18, Bernd : Yeah, I figured it out. In fact I become obsessed with the memory…
Juha Manninen wrote 21 lines
2012/2/18, Bernd : > The text control is for entering the commit message and the combobox > is for quickly selecting one of the previously entered commit > messages. Yeah, I figured it out. In fact I become obsessed with the memory leaks and crashes and started to fix them myself. I think I got them all fixed now. The code become much cleaner by using classes instead of records, and generics containers. Lots of ugly type-casts could be removed. See r35463 and r35469. > Please file a separate bug for every individual problem you find (you > have found at least 3 different problems already) so they won't be > forgotten. I will try to fix them all one after the other and hope > somebody will apply my fixes before it is too late for Version 1.0 You could look at the remaining usability issues. At least the commit msg history list collects duplicate strings. The HourGlass cursor problem seems to be a QT problem. With GTK2 it works better.

What problem with crHourGlass under qt ?

zeljko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120219/1c4770bd/attachment.html>

Reply by email

Juha Manninen
to zeljko

2012/2/19, zeljko :

> The HourGlass cursor problem seems to be a QT problem. With GTK2 it > works better. What problem with crHourGlass under qt ?

In the forms in LazSvn the individual controls' cursor is set to HourGlass and then to normal.
With QT bindings it remains HourGlass forever, at least for TListView and TCombobox. With other bindings it returns back to normal.

I personally like to use Screen.Cursor. It works well also with QT.

Juha

Reply by email

Bernd
to Bernd: ...using gource. Its quite interesting and funny to watch: http://vimeo.com/36868024 Its…

Ok, I made a new one, covering the entire SVN history:

http://vimeo.com/37066125

if playback looks jerky because the flash player seems to need 5GHz to play a a simple 720p video then try to click on the blue HD icon to turn *off* HD (its on by default, even when not watching in full screen) or try to watch it in fullscreen and turn off scaling or just download the source video file and watch it with VLC.

Bernd

Reply by email

Juha Manninen
to Bernd

2012/2/20, Bernd :

Show quoted text 9 lines
Ok, I made a new one, covering the entire SVN history: http://vimeo.com/37066125 if playback looks jerky because the flash player seems to need 5GHz to play a a simple 720p video then try to click on the blue HD icon to turn *off* HD (its on by default, even when not watching in full screen) or try to watch it in fullscreen and turn off scaling or just download the source video file and watch it with VLC.

Nice!
Who is the developer "lazarus" in the beginning, who disappeared around 2003?

Juha

Reply by email

Mattias Gaertner
to Juha Manninen
Show quoted text 13 lines
2012/2/20, Bernd : > Ok, I made a new one, covering the entire SVN history: > > http://vimeo.com/37066125 > > if playback looks jerky because the flash player seems to need 5GHz to > play a a simple 720p video then try to click on the blue HD icon to > turn *off* HD (its on by default, even when not watching in full > screen) or try to watch it in fullscreen and turn off scaling or just > download the source video file and watch it with VLC. Nice! Who is the developer "lazarus" in the beginning, who disappeared around 2003?

At the beginning the lazarus devels had only one account.

Mattias

Reply by email

Mark Morgan Lloyd
to Bernd: Ok, I made a new one, covering the entire SVN history: http://vimeo.com/37066125 if…
Bernd wrote 9 lines
Ok, I made a new one, covering the entire SVN history: http://vimeo.com/37066125 if playback looks jerky because the flash player seems to need 5GHz to play a a simple 720p video then try to click on the blue HD icon to turn *off* HD (its on by default, even when not watching in full screen) or try to watch it in fullscreen and turn off scaling or just download the source video file and watch it with VLC.

Nice. Wonder whether it could be put on a server somewhere, with a new frame generated every time the revision changes and notification of the update sent out via RSS or similar with optional beep at the client?

Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues]

Reply by email