Sequencer - UI display issue

A place to report problems and bugs in SharpCap
Forum rules
‍

If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs

Please also read about Troubleshooting USB Issues before posting.

*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***

Please include the following details in any bug report:

* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
Post Reply
BucketDave
Posts: 23
Joined: Sun Oct 31, 2021 10:50 pm

Sequencer - UI display issue

#1

Post by BucketDave »

This is a minor issue but it would be nice if it was fixed. When i open up the Sequencer Window and run a sequence, the log is updated in the lower right part of the window. If the Sequencer window is maximised, I can see the last entry in the log. All is good.

The bug occurs when I reduce the size of the window (such as you can). The log is not shown properly - i do not see the last entry in the log. Consequently, when i am checking how a sequence is running, i have to have the window at full size. This makes it hard to view info in the main SharpCap window (such as the status bar where frame saves and plate-solves are notified, or the time to end of frame counter (lower right corner)).

I am using the latest version of SharpCap.
User avatar
admin
Site Admin
Posts: 17530
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Sequencer - UI display issue

#2

Post by admin »

Hi,

thanks for the report - I see the same when the window height is close to the minimum height allowed - should be easy to fix, so have a go with the next update and hopefully all will be fine :)

cheers,

Robin
BucketDave
Posts: 23
Joined: Sun Oct 31, 2021 10:50 pm

Re: Sequencer - UI display issue

#3

Post by BucketDave »

Thanks Robin.
Post Reply