I guess that it is what I installed and it works fine on my Win 10 system. Nice icon BTW. Now there is an issue with the mouse pointer in the launcher and all pther images (so maybe a VM problem). The cursor is all black and tiny and has no white surroundings. In a dark theme the cursor is close to invisible. Also the cursor is not obeying the magnification setting of Windows. It worked before. I guess that the cursor masks are not applied properly + other new stuff. That is ruining the whole Pharo experience for me (and I guess newcomers). Phil On Mon, Apr 16, 2018, 16:14 Christophe Demarey <[hidden email]> wrote: Hi, |
Hi Phil,
|
Eliot, Thx for the pointer. This manifest file is new to me. Where is it to be found and what does it do for Pharo? Phil On Mon, Apr 16, 2018 at 5:29 PM, Eliot Miranda <[hidden email]> wrote:
|
In reply to this post by Eliot Miranda-2
I have downloaded the https://github.com/pharo-project/pharo-vm/blob/master/opensmalltalk-vm/build.win32x86/pharo.cog.spur.lowcode/Pharo.exe.manifest and put it in the folder that contains the PharoLauncher Pharo.exe and then the pointers are correct again (they have their masking done correctly. So, there is a packaging issue somewhere for Pharo Windows VMs as downloaded by the Laucher. Phil On Mon, Apr 16, 2018 at 5:29 PM, Eliot Miranda <[hidden email]> wrote:
|
In reply to this post by philippeback
Hi Phil,
On Mon, Apr 16, 2018 at 12:54 PM, [hidden email] <[hidden email]> wrote:
Good!
Indeed, we must include the manifest files on Windows.
On Mon, Apr 16, 2018 at 12:45 PM, [hidden email] <[hidden email]> wrote:
It must lie alongside the .exe. It's an XML file that specifies various runtime environment settings for the executable. i don't know all that it can do, I just know that it does seem whether an application is highDpi aware or not, and your bug report seems to point directly to this. Here's the manifest for Pharo: Pharo.exe.manifest <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3"> <assemblyIdentity version="1.0.0.0" processorArchitecture="*" name="www.mirandabanda.org.Cog.Pharo" type="win32" /> <description>Pharo Smalltalk Virtual Machine</description> <asmv3:application> <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings"> <dpiAware>false</dpiAware> </asmv3:windowsSettings> </asmv3:application> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*" /> </dependentAssembly> </dependency> </assembly> And that reminds me that they need to get updated to refer to opensmalltalk.org!!
_,,,^..^,,,_ best, Eliot |
Hi Phil, Eliot,
I did not get this problem. Is this manifest file new? Is there only one manifest file to include or many? Thanks for reporting this issue. Christophe |
Hi Christophe, What Windows version do you have? I have Windows 10 and a 4K screen. Phil On Tue, Apr 17, 2018 at 9:43 AM, Christophe Demarey <[hidden email]> wrote:
|
Windows 10 on top of virtual box
|
Free forum by Nabble | Edit this page |