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

Cannot scroll to view error messages in build ouptut window #38

Open
csides-hpe opened this issue Apr 13, 2022 · 3 comments
Open

Cannot scroll to view error messages in build ouptut window #38

csides-hpe opened this issue Apr 13, 2022 · 3 comments

Comments

@csides-hpe
Copy link

If a build fails with errors, only the last page or so of error output is visible. The scroll bar for the build output panel does not currently allow scrolling back over the error text.

@vejmarie
Copy link
Member

vejmarie commented Apr 13, 2022

The compiler output is a screen linux command output. So you can use the same trick than with screen command. To access the log you need to press CTRL + a + esc then this will activate your page up / page down keys and you can get access to the whole compilation log. ( @csides-hpe )

@csides-hpe
Copy link
Author

csides-hpe commented Apr 13, 2022

To access the log you need to press CTRL + a + esc then this will activate your page up / page down keys and you can get access to the whole compilation log. ( @csides-hpe )

Good info! I discovered an issue when doing this from a Windows machine, though:

Pressing CTRL + A + ESC works when I'm accessing OSFCI from a Linux machine, but when done on a Windows machine, Windows catches the CTRL + ESC and it opens the start menu instead- so page up / page down doesn't get enabled.

I think it would probably also worth it to eventually add some text to inform users about the hotkeys, and/or a button to emulate those keys being pressed to give scroll access from browsers on Windows machines.

@vejmarie
Copy link
Member

Use a serious operating system :)
We are working at enhancing the learning curve of the workflow by adding "bubbles" which could be activated and de-activated when the end user will have discovered all the 80's cheat codes we have hidden into the UI/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants