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.

Sign up for GitHub

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

Jump to bottom

Need documents #24

Closed
F-TD5X opened this issue May 30, 2018 · 8 comments
Closed

Need documents #24

F-TD5X opened this issue May 30, 2018 · 8 comments

Comments

@F-TD5X
Copy link

F-TD5X commented May 30, 2018

With no documents and GUI I will die when using it...
@cathaysia
Copy link

If you need a install and config documents, maybe ArchLinux wiki:Fcitx5 is a good choice.

@y1wtt
Copy link

y1wtt commented Jun 26, 2020

At the least,I wanna API documentation for creating module.

@wengxt
Copy link
Member

wengxt commented Jun 27, 2020

At the least,I wanna API documentation for creating module.

Well, since we are still under dev, we're sorry for not having documents. Reading existing module code could be a way to do so, otherwise welcome to fcitx@freenode channel.

@y1wtt
Copy link

y1wtt commented Jun 27, 2020

@wengxt Okey, I'll try it! thanks for responding.

@Billy4195
Copy link

@wengxt Would you accept to add an INSTALL file to describe the step to build this project as fcitx5-chewing did?
Because I'm now trying to build this project from source code, but found that there are several required libraries that need to be installed first.
If you accept to add the file, I will try to write down the steps after I built it.

@wengxt
Copy link
Member

wengxt commented Nov 6, 2020

@Billy4195 https://fcitx-im.org/wiki/Compiling_fcitx5

@ThanhPhanTiki
Copy link

Please make some documents ...

@wengxt
Copy link
Member

wengxt commented Nov 19, 2021

I've updated many Fcitx 5 relevant doc on the wiki. Please take a look at https://fcitx-im.org/
There's still some user manual like doc missing. Close for now.

@wengxt wengxt closed this as completed Nov 19, 2021
wengxt added a commit that referenced this issue Jan 15, 2023
@wengxt
Reduce the requirements of unnecessary key event forwarding.
d88a5d5 
In a previous fix of keyboard engine, update preedit to empty is commonly done
to ensure there is nothing in the preedit. This introduces some empty
update preedit for keyboard engine and uses the code path for key event
order fix. This makes almost all key event need to be re-forwarded,
which is unnecssary.

Add a new helper function to check if the strict order matters:
1. all pending events are update preedit.
2. preedit is empty.

If above condition satisfies and we don't need to need forward the key,
allow it to be handled out of order.

Attempt Fix #24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@wengxt @Billy4195 @F-TD5X @y1wtt @cathaysia @ThanhPhanTiki