nosetup_5.0-samandarin-0.1_win_x64 (aka, Tabbed, own Reg Key).zip
Win7, x64
jsonviewer
---
F3 on a 1 GB .json
---------------------------
PrismSharp Text Viewer .NET
---------------------------
The selected file is too large to open. Files larger than 16 MB are not supported.
---------------------------
Understandable.
---
F3 on 4 MB .json
---------------------------
PrismSharp Text Viewer .NET Plugin
---------------------------
Unable to initialize the embedded browser.
Couldn't find a compatible Webview2 Runtime installation to host WebViews.
---------------------------
Webview2, aka MS Edge, again understandable that it won't run on Windows 7.
I OK'd that dialog, RAM rose from ~11 MB to ~50 MB, but otherwise seems like Samandarin would be OK.
-
F3 on a 400 KB .json
Again got the PrismSharp Text Viewer .NET Plugin message.
But this time RAM & CPU started increasing, with RAM seemingly not going to subside, & interaction with Samandarin essentially ended, & I had to kill it.
.
.
-
I suspect /samandarin/ /textviewer/ /webview2renderviewer/ will all do similar.
Not concerned, just pointing out.
Suspect that disabling same might allow something workable (including picking up some ? enhancements over tabbed-salamander-x64-poc-06.zip)?
Tabbed Panels
Re: Tabbed Panels
WinXP Pro SP3 or Win7 x86 | SS 2.54
- KRtek™
- Posts: 16
- Joined: 30 Mar 2008, 20:44
- Location: Brno
- Contact:
Re: Tabbed Panels
Hello therube, thanks for reporting it! I'll take a note in the Github issues - new .NET plugins need code enhancements as currently they are more like prototypes.
KRtekTM, KRtek™
Re: Tabbed Panels
Samandarin, for Win7, how to get something that is workable...
Options | Viewers
if you change any file mask sets that use
JSON, PrismSharp, or WebView2
to something else (Internal or whatever)
that is apt to give you a (so far) working copy, in Win7, of Samandarin
(one that is not apt to crash or hang).
doing that, you'll end up with more functionality
(plugins for one) then with the earlier tabbed-salamander-x64-poc-06.zip
(as before, if you don't have it elsewhere, you might need to copy a copy of vcruntime140_1.dll into the "salamander" directory.)
-
i'll note that every time you open Samandarin, you're notified that the Encrypt / Decrypt plugin is not available.
it would be nice if it only notified... once (or so).
if you were to Plugins Manager -> Encrypt -> Remove...
you'll no longer be notified.
(now, in x64, /plugins/encrypt never was there to begin with, but telling PM to Remove it does work.)
-
you have .svg toolbar icons (& not that i'd use them, necessarily), but how do you go about enabling them?
(or is that a work in progress?)
-
LFN.
what does LFN mean? as in, 32K?
& is that expected to work in Win7?
as in, you cannot copy (F5) a 247-char filename into a 21-char path.
247+21 = 268 which is > the maximum allowed filename length (255),
but certainly less then 32K max.
the Copy should work, or at least (potentially) can - even in Win7.
"Name "247-char..." with full path is too long."
in Win10/11, do you need to set that "LFN" (Registry) entry for it to work?
with that set, will the above example actually work?
(Sally also fails in the same way, for me, on "lfn".)
Options | Viewers
if you change any file mask sets that use
JSON, PrismSharp, or WebView2
to something else (Internal or whatever)
that is apt to give you a (so far) working copy, in Win7, of Samandarin
(one that is not apt to crash or hang).
doing that, you'll end up with more functionality
(plugins for one) then with the earlier tabbed-salamander-x64-poc-06.zip
(as before, if you don't have it elsewhere, you might need to copy a copy of vcruntime140_1.dll into the "salamander" directory.)
-
i'll note that every time you open Samandarin, you're notified that the Encrypt / Decrypt plugin is not available.
it would be nice if it only notified... once (or so).
if you were to Plugins Manager -> Encrypt -> Remove...
you'll no longer be notified.
(now, in x64, /plugins/encrypt never was there to begin with, but telling PM to Remove it does work.)
-
you have .svg toolbar icons (& not that i'd use them, necessarily), but how do you go about enabling them?
(or is that a work in progress?)
-
LFN.
what does LFN mean? as in, 32K?
& is that expected to work in Win7?
as in, you cannot copy (F5) a 247-char filename into a 21-char path.
247+21 = 268 which is > the maximum allowed filename length (255),
but certainly less then 32K max.
the Copy should work, or at least (potentially) can - even in Win7.
"Name "247-char..." with full path is too long."
in Win10/11, do you need to set that "LFN" (Registry) entry for it to work?
with that set, will the above example actually work?
(Sally also fails in the same way, for me, on "lfn".)
WinXP Pro SP3 or Win7 x86 | SS 2.54