It is anti-conventional. Which widely used applications use dynamically sized top or bottom bar? It looks horrible when navigating through directories or image files, and prevents users from using mcomix to comparing images visually (as viewport size become inconsistent). Bottom bar file name looks ugly in case of CJK characters: same font size + extra vertical margin means broken vertical layout. Apparently the text widgets of file names screws up vertical margin for CJK characters. Then the bottom...
It is anti-conventional. Which widely used applications use dynamically sized top or bottom bar? It looks horrible when navigating through directories or image files, and prevents users from using mcomix to comparing images visually (as viewport size become inconsistent). Bottom bar file name looks ugly in case of CJK characters: same font size + extra vertical margin means broken vertical layout. Apparently the text widgets of file names screws up vertical margin for CJK characters. Then the bottom...
It is anti-conventional. Which widely used applications use dynamically sized top or bottom bar? It looks horrible when navigating through directories or image files, and prevents users from using mcomix to comparing images visually (as viewport size become inconsistent). Bottom bar file name looks ugly in case of CJK characters: same font size + extra vertical margin means broken vertical layout. Apparently the text widgets of file names screws up vertical margin for CJK characters. Then the bottom...
Bottom bar height is not fixed and dependent on file names
Does it sound like a way to address your issue? Yes, your proposal surely will solve this issue. My other two cents come from how I used mcomix or how I expected a comic reader to work. (I have no knowledge of mcomix codebase) Caveat: A potential flaw is that the algorithm sketched out above will run into issues if there are more than two pages. Given a sufficiently long but finite sequence of pages, it will get closer to the center of the sequence and then get stuck there. It shouldn't stuck since...
@aasa: Does it sound like a way to address your issue? Yes, your proposal surely will solve this issue. My other two cents come from how I used mcomix or how I expected a comic reader to work. (I have no knowledge of mcomix codebase) Caveat: A potential flaw is that the algorithm sketched out above will run into issues if there are more than two pages. Given a sufficiently long but finite sequence of pages, it will get closer to the center of the sequence and then get stuck there. It shouldn't stuck...
In double-page, let CTRL+switching page always forward one page