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

Legion Enhancement, Cheat sheet update, and more #220

Merged
merged 7 commits into from
Mar 31, 2018

Conversation

LazoCoder
Copy link
Contributor

  • Fixed Issue For people having issues with the grid system (Legion, Douglas, Rainbow) #194
    • Users can now have multiple versions of python installed and not encounter issues with grid systems & asynch tasks (specifically if their environment variables point to a different python version).
  • Significantly enhanced legion's ability to find text with no noticeable difference in speed
    • I experienced issues with the prior implementation of legion where faded out font was ignored and also certain font and background color combinations would throw off the algorithm. This is no longer a problem.
      legion
  • Added "bench" and "squat" which perform "left mouse button down" and "left mouse button up" functions respectively.
    • This is for users who use mouse equipment such as the SmartNav and desire the ability to drag.
    • I chose the words "bench" and "squat" because they are simple, crisp, single syllable words that are related to each other by definition. They are also related to "kick" since they are all athletic movements (easier to remember).
    • I've been using "bench" and "squat" now for a few weeks and haven't had any issues with dragon confusing it with any other words (I'm North American and don't speak with any discernible accent as far as I am aware).
  • Updated the Cheat Sheet
    • (3) corrected “at sign” to “atty”
    • (4) wally
    • (7) bench, squat
    • (9) window snapping

Tested and working fine on my bootcamp installation of Windows 10 on my 15" Mac Book Pro (2015), using Dragon v14.

Lazo added 4 commits March 30, 2018 08:43
If the user has multiple versions of python installed, this will make sure that the correct one is referenced.
The pror legion implementation sometimes failed to find words that had lighter font coloring.
This is for people who use equipment like SmartNav and would like to be able to drag things.
(3) correct “at sign” to “atty”
(4) wally,
(7) bench, squat
(9) snapping
@LexiconCode LexiconCode added Enhancement Enhancement of an existing feature Documentation Issues related to Documentation labels Mar 30, 2018
@LexiconCode LexiconCode requested a review from Versatilus March 30, 2018 15:59
@LexiconCode
Copy link
Member

Very nice work! Everything checks out on my test environment. I would like to get @Versatilus to review before merge as well.

@LexiconCode LexiconCode added Testing Required Requesting testers before merge Complete Pull request is complete and tested as defined by Contributor labels Mar 30, 2018
@chilimangoes
Copy link
Collaborator

Nice work indeed! The one observation I would make is that, at least for me, "squat" would be more intuitive as the mouse down command since I think of squatting down. But it's also not a big deal if you prefer to keep it the way it is.

@BazookaMusic
Copy link
Contributor

Can you add another fix?
At: self.tirg_dll=cdll.LoadLibrary(settings.SETTINGS["paths"]["DLL_PATH"] + "tirg-dll.dll")
convert the whole argument to a string because ,with my path containing unicode, legion crashes.

@LazoCoder
Copy link
Contributor Author

@chilimangoes Sure, that makes more sense. I'll change it.
@gerrish Can you be more specific? Is it this line you want changed? What is the error that you get?

It is more intuitive this way since pressing down and squatting are both downwards motions.
@LazoCoder
Copy link
Contributor Author

I've switched the functionality of bench and squat. Additionally, I've successfully broken down legions rectangles in another branch (as per #126). Here is what it looks like:
split_1
The question is what to do with legion's "light" command. How often do you guys use this? I can remove it, or leave it in, but keep in mind if I leave it in it will now highlight a smaller region. I haven't used it enough to gauge the usefulness of this so any pointers are appreciated.

Alternatively I can leave the original unbroken down rectangle but have it in a different color. This could be used for a greater highlighting area. See the following image to understand what I mean. I made this in Microsoft paint, the three blue rectangles can be used if the user wants to highlight more content than what the smaller rectangles would allow. The number would be on either the right or left side. So for example the user could say "111 light" and it would select 107, 108, 109 and 110 (the whole area).
split_2
But maybe this will look clustered, ugly or confusing for new users? If the highlight command is seldom used then it may not be worth it to add this complexity to both the code and the screen. I haven't implemented this part yet so let me know what you think before I do.

Copy link
Collaborator

@Versatilus Versatilus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is awesome! I'll spend a few minutes playing with it, then hopefully get it merged before midnight GMT.

@LexiconCode LexiconCode added the New Feature A new feature that is not currently implemented. label Mar 30, 2018
@chilimangoes
Copy link
Collaborator

chilimangoes commented Mar 30, 2018

I've rarely used the "light" command. Personally, I would vote for leaving it how it is, with the option of maybe modifying it later to do something like "light one hundred and forty through one hundred and forty four." That shouldn't be hard to implement and would give us the best of both worlds.

@Versatilus
Copy link
Collaborator

@gerrish This is mostly my fault. I'm guessing that in this case the library loader requires a byte string for the path because of ctypes issues. This should be easily fixed by encoding the Unicode string to a byte string based on the file system locale.

Every time I say "again x times" a pop up window would come up and prevent me from performing the given action. This is fixed.
@LazoCoder
Copy link
Contributor Author

Okay so I went ahead and I added in the rectangle division as demonstrated in my previous comment. I left the highlight function as it is.

Furthermore I had an issue where every time I said "again x times" a console would pop up and start printing things to the screen and preventing the function from occurring. This has been fixed.

I won't be adding anything more to this branch so you guys can test it. If there are any issues that you want me to fix let me know.

@LazoCoder
Copy link
Contributor Author

I ran a recursive command to convert all the files to yapf as per the .style.yapf file.

C:/Python27/scripts/yapf -i -r --style .style.yapf -vv *

@LexiconCode LexiconCode removed the Testing Required Requesting testers before merge label Mar 31, 2018
@Versatilus Versatilus merged commit 9285045 into dictation-toolbox:develop Mar 31, 2018
@Versatilus
Copy link
Collaborator

I love this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complete Pull request is complete and tested as defined by Contributor Documentation Issues related to Documentation Enhancement Enhancement of an existing feature New Feature A new feature that is not currently implemented.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants