Two problems in Sigil 2.7.0 in Windows11

[DiapDealer]

That's probably the easiest solution (for Sigil anyway).

Maybe try creating a new user on that machine and see if things work properly for that user? If so, I would think that points to some kind of corruption in your Windows profile.

[BetterRed]

Originally Posted by JSWolf

Do you have these problems if you run Sigil in Safe Mode?

Originally Posted by philja

I don't see any option to start Sigil in Safe mode. How would I do that?

Originally Posted by JSWolf

You run Windows in safe mode. Then you run Sigil.

@philja - before doing anything, I recommend following Jon's suggestion.

Poorly implemented third party shell extensions and start up programs (the applications that show in the tray) have been known to interfere with desktop applications - including Sigil.

Running Sigil in Windows Safe Mode will cut most of those out.

If the problem does not happen in Safe Mode, you will have to determine which third party program is causing the problem. Task Manager can help you do that.

BR

[theducks]

echo %localappdata% returns C:\Users\<NAME>\AppData\Local

is wrong for a typical user

C:\Users\thedu\AppData\Roaming>

is the norm

[DiapDealer]

No. %localappdata% is AppData/Local. Not AppData/Roaming. The clue is in the name.

[BetterRed]

Local is for app data that should not be sync'd to a domain controller - e.g. browser cache, or if the app itself cannot be used in a hotdesk environment… usually licensing restrictions.

Roaming is for app data that can be sync'd to a domain controller so that the app can be used in a hotdesk environment.

It's not obvious to me why Sigil couldn't be used in a hotdesk environment.

BR

[DNSB]

Speaking as someone who used to manage desktops in a corporate environment, getting permission to install Sigil would involve jumping through multiple hoops to justify the install. And roaming data would only be useful if Sigil was installed on every computer in the domain which it would not be.

I was very happy when I was able to move into spending my time on network, storage & security. Machines are so much easier to deal with than users.

Even with 1Gbps connections to the network, with some users deciding to store multiple gigabytes on their desktop, documents, etc., boot times got very slow and SAN storage was being chewed up. The final solution was to limit most users to 200MB of storage for their roaming profiles.

[BetterRed]

Yeah me too, e.g. 40 desks shared by 100 journos, 50 seat 24*7 customer service call centre etc. Hotdesking is not about allowing security to watch the carpark from the COO's PA desktop on the 35th floor.

BR

[DiapDealer]

Originally Posted by BetterRed

It's not obvious to me why Sigil couldn't be used in a hotdesk environment.

Local was chosen long, long ago. Before either Kevin or myself were involved. We're not going to change for change's sake at this point. Anyone who cares enough can easily move their prefs to Roaming (or anywhere else) by setting the SIGIL_PREFS_DIR environment variable.

For what it's worth, the Qt StandardPaths module has changed drastically since Sigil's inception. Using StandardPaths::AppDataLocation (which would return Roaming) was not a Qt recommendation until way into Qt5.x. Qt4.x Sigil used StandardPaths::DataLocation before StandardPaths::AppDataLocation and StandardPaths::AppLocalDataLocation ever existed. Sigil devs simply never saw it as a priority to change it on Windows. Neither do I at this point.