-
-
Notifications
You must be signed in to change notification settings - Fork 327
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
Shortcuts to adjust width size, number of results shown and game mode #1369
Conversation
onesounds
commented
Sep 7, 2022
•
edited by jjw24
Loading
edited by jjw24
- Quick Adjust Width Size by Ctrl + Plus/Minus in query box.
- Quick Adjust Max Result Shown by Ctrl + [ , Ctrl + ] in query box.
- Add Tooltip
- Adjustment adhere to maximum and minimum allowed
- Ctrl + F12 to change to Game Mode
|
I changed it because it was more intuitive to change it like this.
|
Flow.Launcher/MainWindow.xaml.cs
Outdated
if (specialKeyState.CtrlPressed) | ||
{ | ||
|
||
_settings.WindowSize = _settings.WindowSize + 100; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am curious why does this work. I suspect we need to set the property in the viewmodel to trigger change?
…generate RelayCommand)
@onesounds please take a look on my latest change |
It's well organized and the code works well. |
but why the build faild? |
Are we still using Ctrl+ Arrow keys? |
I remove them. |
b1626a7
to
0baf04e
Compare
|
- Size reflect to Slider
Fixed |
Need to make sure the subtitle sentence is appropriate. @Garulf |
|
||
namespace Flow.Launcher.ViewModel | ||
{ | ||
public class MainViewModel : BaseModel, ISavable | ||
public partial class MainViewModel : BaseModel, ISavable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@taooceros why is this changed to partial class?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because I would like to use the mvvm toolkit to simplify the code of creating RelayCommand, which requires partial to generate additional code.
"version": "6.0.100", | ||
"rollForward": "latestFeature" | ||
"version": "6.0.*", | ||
"rollForward": "latestPatch" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@taooceros what's this change for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh it shouldn't be there (I am testing different version of dotnet and see which one can help with the bug. However it is not needed because workaround is found)...Though it makes sense to apply the latest patch since that generally includes some security fixes.
|
||
<Target Name="RemoveDuplicateAnalyzers" BeforeTargets="CoreCompile"> | ||
<!-- Work around https://github.com/dotnet/wpf/issues/6792 --> | ||
|
||
<ItemGroup> | ||
<FilteredAnalyzer Include="@(Analyzer->Distinct())" /> | ||
<Analyzer Remove="@(Analyzer)" /> | ||
<Analyzer Include="@(FilteredAnalyzer)" /> | ||
</ItemGroup> | ||
</Target> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@taooceros What's this change for us specifically?
Updated the wording, hopefully ok. |
I couldn't reply directly. This is a workaround for source generator. Details here dotnet/wpf#6792. If that's being fixed, we can remove it. |
I think it is fixed (in 6.0.400+). However it seems that appveyor hasn't got the latest image. Let's wait a while later. |
Technically it's Ctrl + "=" and Ctrl + "-". |
👍 #1480 |
You guys are too programmers. Why don't you consider the average user? +:increase count. It is a key chosen so that it can be intuitively understood. "Technically it's Ctrl + "=" and Ctrl + "-"." <- This can be talked about. This is because it is not a strong suggestion. Photoshop. I have never seen a case of writing = and - instead of + and - when matching these shortcuts. What stupid program writes shortcuts like this? flow launcher? 😂 |
Lol looking at those screenshots, realised I never paid much attention to how those shortcuts are described, makes sense. Let's revert it back. |
In fact I found it when was looking at my keyboard and realized that + needs a shift combined to input. And I opened powertoys,tried adding some hotykeys, found that they use "=" to describe that key. And I thought every software use "=". Really never paid attention to that. |
So maybe for a single key, = is correct but for pairs like our new shortcut, + and - is a more user friendly choice. |