Circular progress bar

[wolfgan]

I would like to have a circular progress bar. It is not possible to do this on the basis of a circle. I would like to have Pie in the arsenal. Now I'm trying to make progress based on many circles. Approximately in this format:

[matwachich]

Check fyne-x, there is a GIF widget you can use for this.

[wolfgan]

An animated GIF is suitable for an endless operation. But what about showing the percentage of completion? Now I have two ideas: use a set of png slides or try to implement it with many circles (as in the screenshot above).

[wolfgan]

I was able to do what I want.
https://github.com/fyne-io/fyne/assets/7305231/8e9b2866-cc6b-42f6-a8f2-6e279de0eac0

[Jacalz]

I'd say that @wolfgan did the right thing. We place it there (and usually in the constructor as well) so that people can use the widget created with the struct directly if they so prefer.

[wolfgan]

The problem is not in ExtendBaseWidget. The problem is that I cannot access some methods outside the package.

`// Stop the infinite progress bar animation
func (p *DotsProgressBarInfinity) Stop() {
cache.Renderer(p).(*dotsProgressInfinityRenderer).stop()
}

// Running returns the current state of the infinite progress animation
func (p *DotsProgressBarInfinity) Running() bool {
return cache.Renderer(p).(*dotsProgressInfinityRenderer).isRunning()
}`

Animation is in Render. How to access control without using cache.Renderer?
Only because of this I was forced to do Fork. Otherwise, I would make a widget for a fine-x.

[Jacalz]

Ah, I see. There might be a case for rewriting that widget to not interact with the renderer. I've never personally been a fan of doing it the way it is currently set up. Is there any specific reason for doing so? @andydotxyz

[andydotxyz]

You can extend it, replace those public methods in your own code but call the public api from your own code can't you? (Like a delegate pattern).

Perhaps they should look for the cache of p.super() rather than p.

Anyhow it should not require a fork of Fyne - your progress bar could replicate the API instead of extending the existing widgets I would think...

[wolfgan]

In the end, I got rid of this problem. Rewrite without using animation, replacing it with a running line. You can see here
I save the render on creation. Then, using a cast, you can access its methods. Thus, it was possible not to remove the animation, but I could no longer be stopped :)

[wolfgan]

Now it looks like this:

Peek.2023-07-11.21-34.mp4

[Jacalz]

Looks great. Well done