Skip to content

Commit 8e9094c

Browse files
committed
Clarifications.
1 parent d417948 commit 8e9094c

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

README.md

+7-4
Original file line numberDiff line numberDiff line change
@@ -129,13 +129,17 @@ due to bugs in the port of Kivy to the Raspberry Pi you probably need a
129129
monitor with touch-screen support for it to be of much use:
130130
* Although the mouse works, the mouse cursor is not visible, which makes
131131
doing almost anything quite difficult - a touch screen would
132-
work around this issue.
132+
work around this issue. As a temporary measure, I've added code
133+
that draws a small white square under the mouse location while the mouse is clicked (kivy
134+
does not seem to have a mouse motion event that I can use to continuously
135+
plot the location of an unclicked mouse).
133136
* From what I gather the keyboard may also have issues.
134137

135138
If you have Kivy installed:
139+
136140
1. Create a folder called piKam (or anything you prefer). Copy all the piKam files to this folder.
137141
2. Running a server is option, if you want PiKam to work directly without a server
138-
edit the pikam.ini file and make sure the server hostname is blank.
142+
edit the pikam.ini file and make sure the server hostname is blank.
139143
3. In a shell, cd to the piKam folder and enter:
140144

141145
```
@@ -144,8 +148,7 @@ edit the pikam.ini file and make sure the server hostname is blank.
144148

145149
A GUI should fire up. If you're running directly without a server, a preview should be visible.
146150

147-
4. Mousing and clicking around may work, but you won't be able to see the mouse cusor. Control-C (possibly multiple times)
148-
will exit the GUI (hopefully).
151+
4. Mousing and clicking around may work, but you won't be able to see the mouse cusor. Control-C (possibly multiple times) will exit the GUI (hopefully).
149152

150153
(Note that you can't run a Raspberry Pi Kivy client remotely
151154
over the X11 protocal, so you can't work around the problems that way.)

0 commit comments

Comments
 (0)