Hi,

GTK's progress bar has a feature where the progress bar moves left and right repeatedly, instead of the normal from Min to Max.

What do you call that feature and what do you actually use it for? I know I have seen in used in Mozilla Thunderbird as well, but couldn't remember where.

I just implemented a basic TProgressBar widget for fpGUI and wanted to know if that Gtk progress bar feature (running left and right repeatedly) is something people actually use in applications and worth the time implementing in fpGUI.

Regards,
- Graeme -

Graeme Geldenhuys wrote

GTK's progress bar has a feature where the progress bar moves left and right repeatedly, instead of the normal from Min to Max. What do you call that feature and what do you actually use it for?

It's used when the Max isn't known.

Micha

See GNOME HIG:
[http://developer.gnome.org/projects/gup/hig/2.0/controls-progress-bars.html], at the bottom: "Indeterminate-progress indicator".

"
An animated bar indicating only that an operation is ongoing, not how long it will take.
"

Michalis

Well, you can construct black talking cars with it, like the KIT2000 ;-) Saw that on TV once, long ago ;-)

Michael.

Hi,

I have compiled an fpc with revision 5198 bevore 5 minutes for i386-win32 and arm-wince
compiles great. (Actual revisions dont compile)

When i try to rebuild Lazarus or just the lcl for Wince it says:

PPU Loading D:\Programme\lazarus\fpc\2.1.1\units\i386-win32\fcl\zstream.ppu Recompiling zstream, checksum changed for paszlib
PPU Loading D:\Programme\lazarus\fpc\2.1.1\units\i386-win32\fcl\zstream.ppu Fatal: Can't find unit zstream
Fatal: Compilation aborted

but how can it be for an clean compiled fpc ?!
i have deleted all old files.

regards
Christian

I didn't want to mention that, even though it was the first thing on my mind! :-)

Graeme.

It's used when you don't know the time a thing will last (for example, some downloads in FF, or Windows XP boot)
Not sure it's very useful, most of the time i prefer adding a "Kb Downloaded" or things like that to show people that the program is working. My 2 cents ;o)

Thanks Michallis and Micha. I finally understand the KIT2000 feature.

Graeme.

I tend to agree with you. There are many other ways to display that the program is still working. I will add it to the fpGUI wishlist, but there is more important things to complete first.

Graeme.

I just implemented a basic TProgressBar widget for fpGUI and wanted to know if that Gtk progress bar feature (running left and right repeatedly) is something people actually use in applications and worth the time implementing in fpGUI.

There is such feature in Qt progress bar also.
I have used it in a Qt app, and wrote something simillar for a Delphi app. I think this is a nice to have although not very used feature.

Christian Ulrich wrote

When i try to rebuild Lazarus or just the lcl for Wince it says:

.....

but how can it be for an clean compiled fpc ?!

I think you forgot to compile FCL too. You only compiled the compiler and RTL.

Instructions here:

http://www.freepascal.org/wiki/index.php/WinCE_port#Building_FPC_libraries

NO !

please read:
PPU Loading D:\Programme\lazarus\fpc\2.1.1\units\i386-win32\fcl\zstream.ppu Recompiling zstream, checksum changed for paszlib
PPU Loading D:\Programme\lazarus\fpc\2.1.1\units\i386-win32\fcl\zstream.ppu Fatal: Can't find unit zstream
Fatal: Compilation aborted

if zstream.ppu dont exists the error message should look a little bit diffrent or not ?!

have made :
make clean rtl compiler fcl packages utils rtl_install compiler_install fcl_install packages_install utils_install

everythibg builds and install great

then i go to the lazarus dir and call
make

and breaks with this errormessage

Christian

The error message looks like that if the zstream.ppu file is outdated (because then the zstream.ppu file is ignored).

But did it install into D:\Programme\lazarus\fpc\2.1.1\ ?

then i go to the lazarus dir and call make

And does this invocation of "make" use the newly compiled compiler?

Jonas

Thats is not the real problem. Its a bug somewhere in the makefile (look at the .o files, one of them it isn't copied, don't know which one anymore). Thats why compilation fails later. If you manually copy the rtl/units, fcl/units and install the packages wince works..

But did it install into D:\Programme\lazarus\fpc\2.1.1\ ?

YES of course have deleted the old stuff except the bintools and copied everything from d:\pp to d:\programme\lazarus\fpc

And does this invocation of "make" use the newly compiled compiler?

My Path is set to %PATH%;d:\programme\lazarus\fpc\bin\i386-win32 When it woud be so easy i woudnt write to this list but i think its an fpc issue.

Christian

Christian Ulrich wrote

My Path is set to %PATH%;d:\programme\lazarus\fpc\bin\i386-win32 When it woud be so easy i woudnt write to this list

Sorry for trying to help...

Jonas

Thats is not the real problem. Its a bug somewhere in the makefile (look at the .o files, one of them it isn't copied, don't know which one anymore). Thats why compilation fails later. If you manually copy the rtl/units, fcl/units and install the packages wince works..

Thats not for wince thats for WIN32 so maybe someone schould take a look at the makefiles or not ?!
But as i see zstream.ppu and .o and also paszlib.ppu and .o are there

http://www.freepascal.org/wiki/index.php/WinCE_port#Building_FPC_libraries

D:\Programme\lazarus\fpc\2.1.1\units\i386-win32\fcl\zstream.ppu

> Recompiling zstream, checksum changed for paszlib > PPU Loading

D:\Programme\lazarus\fpc\2.1.1\units\i386-win32\fcl\zstream.ppu

There is heavy work ongoing so don't depend on working with trunk currently.

Thats is not the real problem. Its a bug somewhere in the makefile (look at the .o files, one of them it isn't copied, don't know which one anymore). Thats why compilation fails later. If you manually copy the rtl/units, fcl/units and install the packages wince works..

Havend copied all units from source\fcl\units to units\fcl and from source\packages\base\paszlib to units\paszlib

the same problem. can nobody confirm this ?

http://www.freepascal.org/wiki/index.php/WinCE_port#Building_FPC_libraries

D:\Programme\lazarus\fpc\2.1.1\units\i386-win32\fcl\zstream.ppu

> Recompiling zstream, checksum changed for paszlib > PPU Loading

D:\Programme\lazarus\fpc\2.1.1\units\i386-win32\fcl\zstream.ppu

yes but there are some lovely stuff on the trunk ;) like working debug symbols with the internal linker and so on

> My Path is set to %PATH%;d:\programme\lazarus\fpc\bin\i386-win32 > When it woud be so easy i woudnt write to this list Sorry for trying to help...

dont be worry please, maybe ive writed a little bit hard. iam glad that you all try to help.

you wrote

yes but there are some lovely stuff on the trunk ;) like working debug symbols with the internal linker and so on

If you want a 'stable' trunk stick with r5191 for now.

Peter

.. but don't use smart-linking (-XX) then.

better use r5180 ..

regards
Burkhard

ok, i havend belived this but seems to be an compiler issue maybe the ppu check code is broken in revisions >5191 or something else with 5180 everything seems to build clean thanks.

is it possible to make a list of "tested" revisions. i would like that i like to use an mostly actiual revision to have advance of its benefits.

regards
Christian

Christian Ulrich wrote

is it possible to make a list of "tested" revisions. i would like that i like to use an mostly actiual revision to have advance of its benefits.

Maybe you could start that to the wince page on the wiki:

http://www.freepascal.org/wiki/index.php/WinCE_port

If you want tested revisions use the releases. For trunk you are on your own to keep track of working revisions. Maybe for you rev A is good, but broken on an other platform where rev B is better.

Peter

If you want tested revisions use the releases. For trunk you are on your own to keep track of working revisions. Maybe for you rev A is good, but broken on an other platform where rev B is better.

Not all realeases are stable,i have used fpc 2.0.4 for 2 days and then used fpc 2.1.1
because fpc 2.0.4 breaks compiling my apps often with "internal compiler error"
fpc 2.1.1 has support for the internal linker and so on. iam search ca once a month for an "stable" fpc trunc and use them where i update lazarus dayly and
switch to the previous revision when it dont run clean.

I think a lot of people do this like me, and its easyer when they can look at an fpc wiki page
where they find the last revision tested from some people.

@Felipe, i dont want this only for wince.
for win32 and win64 fpc > 5091 is also not useable. think an general wiki´page in the fpc wiki is better for that or not ?!

5080 is now tested with win32 win64 and wince, make install fails on exampleinstall
but the compiler fcl and rtl compiles,installs and works fine as i can see.

Christian

Having such a page is not bad but I consider it more as something which can be done by the power users instead of the developers. If something serious is started, I'll link it to the main page.

Christian Ulrich wrote

@Felipe, i dont want this only for wince. for win32 and win64 fpc > 5091 is also not useable. think an general wiki´page in the fpc wiki is better for that or not ?!

Yes, could be. Each revision would then have a note saying on which targets it was tested.

Not sure where to put a link to this page, surely not on the main page.

I created such page here:

http://www.freepascal.org/wiki/index.php/Tested_Unstable_Revisions

I linked it from the FPC wiki page, instead of the main page, because I consider it not important enougth for the main page.

I will also add a link on the WinCE page

I created such page here: http://www.freepascal.org/wiki/index.php/Tested_Unstable_Revisions

Please don't use something like
... and higher
but a range instead:
5091 to 5114 - unusable on win32, win64 and wince

If it's later fixed people might think, it's still not fixed.

I linked it from the FPC wiki page, instead of the main page, because I consider it not important enougth for the main page. I will also add a link on the WinCE page

thanks for the hint, fixed.

That should only be changed after it's fixed I think, because if you write "5091 to 5114" and it's still not fixed in 5115, people may also be confused :)

Jonas

It just says those revisions are unusable, not whether the others are or are not.

Micha

To be on the safe side, add a hint: revisions not listed, may work or not, they are simply not tested :)

Having such a page is not bad but I consider it more as something which can be done by the power users instead of the developers. If something serious is started, I'll link it to the main page.

right, but i think the "power users" read this list so i hope tht they will help stay tuned with an site.

< Charset 251 unsupported, skipping... >

Btw, what is that charset 251 in your header for a charset? :-)