-
Notifications
You must be signed in to change notification settings - Fork 47
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
[WIP] Adding Display Page (without Night Mode) #295
[WIP] Adding Display Page (without Night Mode) #295
Conversation
Maybe I miss to develop screens positions (to show who's primary, etc) on multiple screens but I haven´t any design model to do that, did you have that ? |
I'm on it. Some Yaru widgets aren't optimized for responsive, in this case in YaruRow widgets and Yaru buttons |
Best is if you use the kDefaultWidth for the section. Then the rows should follow |
I've just pushed a fix for overflow. Remark : I think it can be an issue because we may loss model data on resizing |
Hi @atsen-dev I don't know if this is related to your last commit or if this is a result of using the page at all but the page does not load anymore and I receive this error:
any idea why this is happening? Different topic: could you move what you have currently in "api" into the service dir? Maybe make a subdir "displays_service" or something. I want to move the "Pdf api" also. Because none of those are actually an API :) |
It is intended that the models are reloaded on build. Maybe you need to move more data to the service instead then. And sorry for the late reply :) |
Yeah for sure. If you have others issue, please put logs here, it will be helpful Thanks |
For this issue, I didn't have that in my case. Can you please send me what you have as data in "lib/api/display/display_api.dart" at line 54 ? Maybe you can have that in debug mode. For now, i'll fix it to avoid that issue. |
|
804ee3d
to
ffa0dae
Compare
Hello, I'm not able to reproduce your issue. I have pushed a(n eventual) fix to avoid that type of crash. (Sorry for my english) Thanks |
@Feichtmeier Can you answer to that comment all remark about UI and interface, disposition of buttons etc ? |
ffa0dae
to
e8badf1
Compare
Np about your english, mine is not perfect as well ^^ My getCurrentState() return value:
For some reason it worked on the first test but then it suddenly stopped working. I can no reproduce what exactly on your page caused this but I still have the same error as posted above. I retry in a fresh VM So since I can not see anything I currently can not comment much on the design. I test in a fresh VM now |
okay I think I need to checkout your branch again. somehow I didn't get your last commits |
Can you confirm that it's data you have when you have you built-in disabled and your external enabled ? |
Ran it again just now with internal disabled via lid-close and external monitor active just to be sure:
|
The error still happens but I can fix it with openening the lid again. Then it doesn't matter if I close it again |
Okay, thanks, I think I know how to solve that. This issue happen because it didn't find any option as current. |
It's caused by the ListView, I'll fix size with a SizedBox ;) |
I just have pushed new things to fix your issue + expansion of section. ;) Can you check and say me if that's good ? |
Great !! Fractional Scaling ? Maybe we can push that an append fractional scaling after ? |
Maybe instead of |
Seems to be same for me. Usually I have seen "100%" but why not. @Feichtmeier what do you think about that ? |
It would take less space if we keep it in the toggle buttons |
I am fine with both. Or you could use a slider. But go with whatever you like. For the apply button I would use an ElevatedButton, since it's green :) Position is okay I guess |
I really like the idea of slider for scaling range :D |
I guess it would be useful for fractional scaling. |
On the other hand a slider with two values looks silly. Let's go with this one for now |
Indeed, you're right. |
Is it ready to merge? |
sorry didn't see this comment Fractional scaling seems like a big second task yes. Also we could eventually think about some drag and drop widget to arrange the displays to each other. Both could be done in different PRs |
Okay great. For me, ready to merge. |
Apart from that. I recommend you to be sure no Pull Request can't be completed if there's issue in analyzer. |
Thank you very much for this huge work @atsen-dev 🙇 |
Okay, we should fix this in the CI I guess |
..added generated_plugins.cmake, doesn't hurt
Regression introduced in #295
Page 1
Page 2
Page 3
Page 4
Page on modify
Work already in progress to tests and verify all is working on multiple screens + some documentation to make it complete
Ref #58