-
-
Notifications
You must be signed in to change notification settings - Fork 342
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
ContentView left inset of -8 #551
Comments
Hello, While this is a bug, the reason why this was needed is for other layouts, and I guess I didn't properly gate it to those situations. |
Hey, thanks for the quick reply! We are indeed using a |
Just an aside, but any reason you are not using the standard prominent style? You should be able to achieve your current look. You can customize font, colors, etc. |
Not that i know of, i inherited the project unfortunately. But it might be worth looking into now that you mention it. |
Please try with the 2.16.5 release. |
I do suggest using the standard layout styles as much as possible. https://github.com/LeoNatan/LNPopupController#bar-style In addition to getting a lot of behavior "for free", they are also the most maintained, and are very customizable, so you can achieve a lot with them. |
Amazing man, thanks a lot for the quick response and fix! |
Cheers! Happy coding! |
Describe the Bug
The _LNPopupBarContentView leading inset is suddenly inset out of view.
Our project was on version
2.15.4
and i updated to2.15.24
and the issue arose. I pinpointed it in the2.15.22
release where a left inset is set on the contentFrame of-8
.I think this is the line affecting us
2.15.21...2.15.22#diff-4f6881108fb36c4b054ad3dba6575391825d8cf796acfb1b62e2482ab309364dR554
I updated to the latest version,
2.16.4
, to check if it was fixed there, but it wasn't.Expected Behavior
I don't expect the view to change insets on an update 😛
Screenshots
![Screenshot 2023-11-24 at 16 01 03](https://private-user-images.githubusercontent.com/124164790/285490390-97deb997-4eb0-4a45-b088-dcdbd41539ba.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjEzNTEzMTIsIm5iZiI6MTcyMTM1MTAxMiwicGF0aCI6Ii8xMjQxNjQ3OTAvMjg1NDkwMzkwLTk3ZGViOTk3LTRlYjAtNGE0NS1iMDg4LWRjZGJkNDE1MzliYS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzE5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcxOVQwMTAzMzJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lYTI2MjA1ZGRmMzcyZTE2NmFlMjkyMTM3YmQ5OTE4ZDU5ODgwMzI4ZDM1MGIyYzY4MTk4YWNkYjRhNDFmYmI3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.Gqi895_rztGhsoDWixwqX2PjVfwV2Dyw35HSKKaghBo)
Additional Context
I really wonder why you decided to add this inset. Next to that, what would a proper solution be for our project?
The text was updated successfully, but these errors were encountered: