Skip to content
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

[REQUEST] More Concise LockScreen README Wording #213

Open
ghost opened this issue Jul 10, 2021 · 1 comment
Open

[REQUEST] More Concise LockScreen README Wording #213

ghost opened this issue Jul 10, 2021 · 1 comment

Comments

@ghost
Copy link

ghost commented Jul 10, 2021

Is your feature request related to a problem? Please describe.
I want to apply a lock screen to an ISO build and I find that the README is vague in its instructions. The README says that it must be a JPG though it doesn't specify if it can be a progressive JPG or not. Additionally, where it says that the image must "have dimensions appropriate for the resolution (1920x1080)", it makes it seem as though I need a 1920x1080 JPG though I have doubts as I'd assume 4k JPGs should allowed. It is unclear to me as to whether or not 1920x1080 is the minimum requirement or if I can go higher.

Describe the solution you'd like
I would like to see the README elaborated on more clearly as I find myself confused when it comes to converting the wallpaper I plan on using to become the lock screen image.

Describe alternatives you've considered
N/a

Additional context
N/a

@ghost ghost changed the title [REQUEST] More Concise LockScreen Wording [REQUEST] More Concise LockScreen README Wording Jul 10, 2021
@ghost
Copy link
Author

ghost commented Jul 11, 2021

Update: After attempting to run Optimize-Offline with a 3991x2245 JPG wallpaper (I can't remember if it was progressive or not) it seems to have worked out fine. That being said, I still feel as though the README with the "dimensions appropriate for the resolution (1920x1080)" is misleading and should be better elaborated on further as it still comes off as kind of vague.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants