Let's start a new thread for this.
Attempting to load externals of the wrong type
just gives those vague 'unable to load' errors.
I have some cross-platform CPU architecture detection code which I code
port to Pd, so that we could have more descriptive error messages.
Help->About Pd gives: "Pd version 0.50.0", maybe it could say "Pd
version 0.50.0 (64-bit addressing)".
IMO, it doesn't really fix the undescriptive error messages, because the
user has to know in advance that the problem is about 64 bit/32 bit,
before they even look for that info. Also, they don't always know at
first glance if the externals are 64-bit or 32-bit...
I'd still like to see "Pd version 0.50.0 (64-bit)", though.
Christof
On 28.05.2020 17:59, Martin Peach wrote:
On Thu, May 28, 2020 at 11:36 AM Miller Puckette via Pd-dev
<[email protected]> wrote:
This will sound precious, but I have a policy of pushing back against the
forced-upgrade pratcices of Microsoft and Apple. I suspect many people outside
of Europe/North America are using very old machines.
At any rate, I now plan to put out a 64-bit test version compiled with IPV6
support (-DWINVER=0x0600 -D_WIN32_WINNT=0x0600 as Iohannes suggests), and
later
go back and provide XP versions in 64 and 32 bits.
Is there any way for a user to know if their version of Pd is 32 or 64
bit while it's running? Attempting to load externals of the wrong type
just gives those vague 'unable to load' errors. If the 'About PD'
window would say which address size it uses that could help. (I use
different versions on a few different machines and I can't remember
which is which)
Help->About Pd gives: "Pd version 0.50.0", maybe it could say "Pd
version 0.50.0 (64-bit addressing)".
Martin
_______________________________________________
Pd-dev mailing list
[email protected]
https://lists.puredata.info/listinfo/pd-dev
_______________________________________________
Pd-dev mailing list
[email protected]
https://lists.puredata.info/listinfo/pd-dev
