Eclipse Community Forums: Papyrus for Real Time

Home » Eclipse Projects » Papyrus for Real Time » User Input(Ways of getting user input that doesn't require constant listening)

Show: Today's Messages :: Show Polls :: Message Navigator

User Input [message #1769828]

Thu, 03 August 2017 19:34

Christopher Won

Messages: 11
Registered: July 2017

Junior Member

I'm trying to think of a way of getting user input that doesn't require the program to be constantly listening for key presses as this holds up the rest of the events happening

An example of the problem I am currently having is that I have a timer which controls the movement of an automated zombie (it just moves until it reaches a wall, turns around and moves the other direction repeating this). In another capsule I have a state that uses fgetc to get user input on how to control the player character. This however raises the problem in which fgetc waits for user input and so while its waiting for user input, the automated zombie can't move, once an input is read by fgetc, the automated zombie moves one step and then it produces errors as the state diagram is not ready for another timeout

I currently can't think of any way around this problem as getting user input requires the program to be listening for key presses or a specific key press

Any help would be greatly appreciated

Report message to a moderator

Re: User Input [message #1769833 is a reply to message #1769828]

Thu, 03 August 2017 21:17

Charles Rivet

Messages: 219
Registered: May 2014
Location: Canada

Senior Member

The easiest way wold be to have the "UI" listening for key presses on a separate thread from the rest of the application.

Check out the Thread Assigment topic in the Papyrus-RT wiki to see how you can assign different parts of your model to different threads.

In more industrial contexts, the User interface would be in a separate executable and it would connect through some commincation chanel (IPC, named pipes, CORBA, etc.)

/Charles Rivet

Report message to a moderator