Comments on 0.97

[tperry2x]

Please place any comments regarding v0.97 of OpenXTalk Lite here, and I'll do my best to look at them in the new year. All the best to everyone, and happy testing
https://www.openxtalk.org/forum/viewtop ... 4646#p4646

[richmond62]

Cripes . . . that's pretty quick.

Downloading at the mo': comments may take longer than with 0.96 as have my sons here and so on.

on Mac still says: 0.0.9.5

Oh, shags:
-

Screenshot 2023-12-26 at 11.01.27.png (48.71 KiB) Viewed 969 times

-
Hmm . . .
-

Screenshot 2023-12-26 at 11.09.22.png (221.71 KiB) Viewed 967 times

-
MacOS 12.7.2
-

festivekim.jpg (49.75 KiB) Viewed 963 times

[tperry2x]

I'm confused. Just did a test of the dmg, extracted on my old mac:

097test.png (474.17 KiB) Viewed 959 times

Just to check I'm not going mad, I also just checked this on my MacBook Air:

097test2.png (909.57 KiB) Viewed 957 times

Apart from a small "verification" delay... then opened, and opened successfully thereafter.
However, it shouldn't be doing that, so I'll need to try re-codesigning it again and uploading a replacement copy... blast

097test2-b.png (378.78 KiB) Viewed 957 times

I'm assuming you see v0.95 on the get-info dialogs? every time I mess around with the plist, it breaks the codesigning, and I probably broke it again when setting it to 0.9.7. So I reverted my plist to an earlier copy (which it also seemingly didn't like ).
I may in future just keep it at 0.0.0.9 and 0.0.1.0 for the mac in the get-info dialogs (plist file), so to stop this kind of thing happening repeatedly. Even if we are at 1.9 it'll say 1.0 in the cmd-i (mac get-info dialog in the finder) because it's a pain to keep remembering to re-apply the codesigning each time.

Anyway, new version incoming.

[tperry2x]

Have re-codesigned this again.
...It's always the mac version isn't it...
Uploading a new copy to replace the old one.

please-wait.png (63.58 KiB) Viewed 948 times

[richmond62]

Probably will be able to look at it tomorrow afternoon.

[tperry2x]

Righto. No rush - here's hoping this one works better for you.

[richmond62]

Just popped into my school for a few things, so am downloading the newer 0.97 to see if it will start on MacOS 14 Sonoma . . .

.It's always the mac version isn't it...

So it would seem: I wonder how those "on the other side" manage 'things'?

F*ck a Duck:
-

SShot 2023-12-28 at 10.59.07.png (57.92 KiB) Viewed 917 times

-

SShot 2023-12-28 at 10.59.53.png (123.95 KiB) Viewed 916 times

-

whpsNch.png (256.62 KiB) Viewed 913 times

-
I am not holding my breath for when I try that on MacOS 12 at home later today.

Never mind: as you already know I'm "as kinky as hell", and will keep trying whatever versions you throw at me.

ESPECIALLY as want to check out your changes!

[tperry2x]

...Never mind: as you already know I'm "as kinky as hell", and will keep trying whatever versions you throw at me.
ESPECIALLY as want to check out your changes!

haha, in that case, let me tempt you over to the Linux side as your mainstream computer!
Seriously though, I'm rapidly becoming pi$$3d off with MacOS.
Please try importing the certificate into your 'login items' keychain. If that doesn't work, I'll pass signing of this mac version over to someone else to struggle with.

[richmond62]

If you look at my last-but-one image, that was what happened when I double-clicked on the certificate.

[richmond62]

I have 2 laptops running Linux; my 'problem' is NOT with Linux, it is with laptops: just do not like them at all.

[richmond62]

I think the word you want is 'deprecated', not 'depreciated'.

[richmond62]

And so, here "we are", on MacOS 12.7.2 and wondering why the flying tiddleypoms the certificate will not be accepted:
-

Screenshot 2023-12-28 at 19.37.55.png (363.81 KiB) Viewed 893 times

-
Is it "just" my system, or does it fail on other people's Macs?

[richmond62]

AND, as I managed to get 0.96 working perfectly well on both MacOS 12 and MacOS 14: what on earth did you DO that fudged 0.97?

Please give this some careful thought before you start shouting 'deprecated', or even 'depreciated'.

[tperry2x]

I think the word you want is 'deprecated', not 'depreciated'.

Screenshot at 2023-12-28 18-01-12.png (20.68 KiB) Viewed 888 times

Strongly disapproved of... (not really)

Screenshot at 2023-12-28 18-00-49.png (16.03 KiB) Viewed 888 times

Reduced in value over time... Yes, this is a good way to describe the state of MacOS.

[tperry2x]

AND, as I managed to get 0.96 working perfectly well on both MacOS 12 and MacOS 14: what on earth did you DO that fudged 0.97?
Please give this some careful thought before you start shouting 'deprecated', or even 'depreciated'.

I did everything that I normally do when producing something that might stand a chance of running on CrapOs.

Never mind.

[richmond62]

"Over there" and in America generally, re software, they seem to use the word 'deprecated'.

Personally I would choose neither of those words, and rather favour a direct phrase such as "no longer supported", "no longer works",
or "you've had your chips".

Never mind.

But I do, desperately.

[tperry2x]

But I do [mind], desperately.

My current plan is to re-upload the 0.96 mac version (because I know it worked),
https://www.dropbox.com/scl/fo/0g093509 ... hqhd8&dl=0
...and then post alongside it the changes needed to make it into 0.97. Mac users can update it themselves, and perhaps they will have more luck.

If you already have 0.96 mac version floating around, just download the changes to make it into 0.97 here:
https://www.dropbox.com/scl/fo/2of5iwre ... pbc5t&dl=0

[richmond62]

Thank you for that: downloaded and first on my list for tomorrow.

[tperry2x]

All help greatly appreciated if someone else wants to pick up the job of maintaining the mac version

poster-wanted-oxt.jpg (78.4 KiB) Viewed 870 times

[richmond62]

I hope I am not being targetted.

Currently working with my chainsaw in the neighbours' garden (them being in their 90s) removing most of a walnut (sad) that was destroyed by a heavy snowfall we had two sennichts syne.

As thee, and anyone else bothering to look, will have jaloused, my 'rmCode' was a model of how to get up the wrong tree without a chainsaw.

So, I am NOT thy Mac-man, although, paradoxically, I do wear a Macintosh hunting kilt, my maternal gowfer being one Richmond McIntosh from the Isle of Bute.

HOWEVER, I shall play swap-arounds tonight, and should that suffice, it might be a grand idea to keep making Mac versions by sequential twiddling with 0.96, rather than going for full builds, or whatever you have been doing to produce non-functional Mac builds, and get you in a foul temper.

Right, I have had my mid-yoken, so I am off to the walnut tree again, first with the chainsaw and then with the 'Nunga muncher' to turn the thinner branches into mulch.