-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
type definition ordering strangeness #13
Comments
Another strange thing in type ImageFill int
type ImageScale int32
const (
ImageScaleSmooth ImageScale = iota
...
)
const (
ImageFillStretch ImageFill = iota
...
) |
Lastly in func (g *boxLayout) isSpacer(obj fyne.CanvasObject) bool {
...
}
func NewHBoxLayout() fyne.Layout
func NewVBoxLayout() fyne.Layout |
I will take a look as soon as I can - Fyne is a great source base to make this kind of tests. |
metal3d
added a commit
that referenced
this issue
Jun 26, 2023
With no pointer receiver or return type, the constructors and methods were not detected. See #13 - on the comment #13 (comment) - the problem seems to be resolved for this case. TODO: vars are not joined, a new line appends after each...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Applying the latest version in Fyne's
geometry.go
I see the following order of public types:After this the type methods are added. I'm not totally sure, but this seems not quite right...
The text was updated successfully, but these errors were encountered: