Universal Viewer - Lister alternative

[Clo]

2Alextp

Hello Alexeï !

• Preview colours on the buttons themselves would be nice !

• BTW :  I discovered why the local-menu doesn't work here in text mode !
- Simply, it's by using the old <riched32.dll> from <icfu>.
- If I rename it, the menu works alright, but indeed the light flickering comes back when selecting …
- May I hope that this issue'll disappear when you'll have changed the text-mode ? I guess it should…

 KR
Claude
Clo

[majkinetor !]

Alex, what is the problem in implementing folder plugins ? Isn't that the same as for files ?

[Alextp]

2majkinetor !
Problem is: Viewer has checks for file existing before passing name to internal functions.
If I comment these checks, then user will suddenly open invalid typed filenames (with no result).
If I make checks for existing of file *or* folder, then... then maybe OK.. I'll see...
l

[Clo]

2Alextp

Hello Alexeï !

• I noticed a trivial issue :

- The middle Win button (restore¦maximize) doesn't work in the viewer.
- Is it by design ? In the case, I needed to display two pictures with the viewer and another programme, and I could not…

 KR
Claude
Clo

[Alextp]

2Clo
No, it should work. Works Ok here. Strange..
(Maybe, some plugin blocks this button?)

[Alextp]

1.4.7.3 (15.07.06):
- auto-detection of Unicode files (both Little-Endian and Big-Endian)

[Clo]

2Alextp

Found ! When the programme is displayed, there is not any "normal" size already stated by default (In the INI?), so it fits the screen even when pressing the WMB.
Hence, I couldn't catch the adjustable borders, they are not reachable the first time you start the viewer…
- I had to shift it a bit via D&D from the title-bar to reduce the window, then it remembers the "normal-adjustable" size…
… but the first situation comes back if you close the window while it's maximized… The MWB doesn't restore the "normal" size, I ought to shift it again and so on…

 KR
Claude
Clo

[Alextp]

2Clo
Ok, understood..
Clo, this is because Viewer remembers only last poistion on close (even if it was maximized!). So, closing in max. state leads to unworking "Restore" button...

[Vansumsen]

2 Alextp

I can confirm the issue with the M.W.B., and I consider it's an annoying bug

- I never saw any programme that behaves such as…IMHO, the "normal / adjustable" size might be saved also in the INI, and used when I ask for that display, even if I have closed the viewer formerly while the window was maximized.

Please, could you fix this ?

TIA !

Friendly

Paul

[Clo]

2Vansumsen

Hello Paul !

• Thanks to check this ! It's indeed very annoying…

- Like I said above, I think that a default "normal" dimension might be set in the INI prior.
- Let's say, i.e. 600*300 pixels (allowing to catch the borders even with a 640*480 screen definition…), and remaining available and functional each time we press the MWB…
- Moreover, the position as reduced could be defined too (centred, UP-L, UP-R etc. )

 Friendly,
Claude
Clo

[Alextp]

Ok, I can save to ini "normal" sizes, when Viewer is closed in maximized state.
I'll take it as about 600x400.

[Clo]

2Alextp

Thank you ! This'll be of course much handier !

- 600*400 could do the trick. Naturally, I don't think that many users have 640*480 currently, but this is set while you boot as "Safe mode" when a problem occurs in Windows; and in such a case, the viewer could be used to check some files…

 KR
Claude
Clo

[Clo]

2Alextp

Another detail in the last version :

• A UTF8 text-file is displayed quite fine. But in the Option menu, I've the "Plain text" entry ticked…
- In F3, I get alright :  "UTF-8  7" marked with the full Ex-Or bullet • . But the viewer uses this "7" entry for the plugins…
- So, I think that a "8" entry should be added. It could match very well with UTF-8 and doesn't need a translation.
What do you think ?

 KR
Claude
Clo

[Alextp]

Agree that it should be added.
But I think how to add it:

6 Unicode
7 Plugins
8 UTF-8

or

6 Unicode
7 UTF-8
8 Plugins

or

6 Unicode/UTF-8
7 Plugins

[Clo]

2Alextp

I would vote rather in favour of the first order, because "8" for UTF-8 is easy to remember, and has just to be added at the end of that menu-section, no need to move the others…
- It's better to distinguish Unicode (16) and UTF-8, because in TC, some functions don't support that format yet {*} and it's important to detect it (i.e. : For compare by contents…) while UNICODE is supported.
{*} … And it shall not be supported still there in the future 7.0…:|

 KR
Claude
Clo