-
Notifications
You must be signed in to change notification settings - Fork 26
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
message line will not apear on a new line (on Windows 10?) #8
Comments
I guess we need a little more management of the output line state? I don't use msg() myself any more, so I didn't notice it was working like this. |
I looked at the code on my fork. def start_on_new_line(self):
""""check if to fill in a \n to start on a new line with the following output.
"""
if self.inside_line:
self.inside_line = False
self.prout('', end='\n')
def msg(self, s):
self.start_on_new_line()
self.prout("Message: "+s) I am now looking at the test cases. |
42sol-eu
changed the title
message dialog will not apear on a new line (on Windows 10?)
message line will not apear on a new line (on Windows 10?)
Dec 9, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
if I use the
cog.msg( ... )
the first call will be directly printed on theCogging ...
output line.Every following message will be printed on a own separate line.
Suggestion: Add a new_line to the Cogging output
The text was updated successfully, but these errors were encountered: