It is possible to do some rearranging of menus etc but as Spragleknas has said it requires editing the xml files for the skin you are using.
I have recently made changes to some xml files to relocate some buttons etc to make the interface less confusing.
I am not familiar with xml but found the changes quite easy to do but this is dependant on the skin you use. I used to use XFACE skin but as I dont know xml I found it difficult to interpret the xml files.
I recently made the switch to the MONACHROME skin which is much easier to understand and also has some extra menus that are added as plugins providing more flexibility.
Have a look if you're interested. If you are not familiar with xml then I will try and help as much as I can but as I said I am new to xml and so can only do basic things at the moment.
100% my bad - as expected :)
So, I had disabled the Windows Update service. Not a wise move, until MP all installed and working nicely. The reason it failed is because DotNetFrameworkChecker.cs looks in Registry HKLM SOFTWARE\\Microsoft\\NET Framework Setup\\NDP for v4/v4.0 AND v3.5. W10 has V4.0 but not 3.5. MP installer...
100% my bad - as expected :)
So, I had disabled the Windows Update service. Not a wise move, until MP all installed and working...
Just tried a new Client-only install on a clean Win10 Pro box. Installer doesnt realise .NET 4 Framework already 'installed' (part...
According to Wikipedia, Windows only uses code pages other than UTF-8 to support legacy (mostly 32 bit) applications and supports two code pages in addition to UTF-8 (OEM and ANSI). According to Microsoft, UTF-8 has been the preferred character set since 2019. If TV Server (or its import routine) were using UTF-8, then umlauts...
According to Wikipedia, Windows only uses code pages other than UTF-8 to support legacy (mostly 32 bit) applications and supports...
Because I have around 200 TV channels and more than a dozen groups, I tried to import the TV channel groups from an old export.xml...
Those folder's last modified time isn't really accurate it seems. Latest change was a merge from PR #384 on may 3rd which was exactly that fix, see f.e. MediaPortal-1/mediaportal/MediaPortal.Application/MediaPortal.cs at 8fa4ccca20059a5534a029266efa596e83387f5b · MediaPortal/MediaPortal-1
Those folder's last modified time isn't really accurate it seems. Latest change was a merge from PR #384 on may 3rd which was...
Now that MediaPortal has gone 64-bit, any references to lParam should be converted to int64 rather than int32 or compared to zero...