Not work on Catalina 10.15.2

[grafikartes]

worked perfectly on 10.15.1, after upgrading to 10.15.2 crashed, Someone with the same problem?

[zhizhi-dev]

+1

[mrgooge]

same here...Maybe this will help

Thread 2 Crashed:: Dispatch queue: NSOperationQueue 0x7fb1980405e0 (QOS: UNSPECIFIED)
0 com.apple.CoreFoundation 0x00007fff2d4f2cff CFArrayGetCount + 6
1 com.apple.bom 0x00007fff421c8345 BOMCFArrayMaxRange + 9
2 com.apple.bom 0x00007fff421de347 BOMTreeIteratorNew + 85
3 com.nilsen.ThemeKit 0x000000010c7965ec -[TKAssetStorage _enumerateFacets] + 172
4 com.nilsen.ThemeKit 0x000000010c7963c7 __35-[TKAssetStorage _beginEnumeration]_block_invoke + 55
5 com.apple.Foundation 0x00007fff2fbda79d NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK + 7
6 com.apple.Foundation 0x00007fff2fbda695 -[NSBlockOperation main] + 98
7 com.apple.Foundation 0x00007fff2fbda620 NSOPERATION_IS_INVOKING_MAIN + 17
8 com.apple.Foundation 0x00007fff2fbd9814 -[NSOperation start] + 731
9 com.apple.Foundation 0x00007fff2fbd952e NSOPERATIONQUEUE_IS_STARTING_AN_OPERATION + 17
10 com.apple.Foundation 0x00007fff2fbd93f8 __NSOQSchedule_f + 182
11 libdispatch.dylib 0x00007fff64b65134 _dispatch_block_async_invoke2 + 83
12 libdispatch.dylib 0x00007fff64b5950e _dispatch_client_callout + 8
13 libdispatch.dylib 0x00007fff64b5b6c0 _dispatch_continuation_pop + 414
14 libdispatch.dylib 0x00007fff64b5adbe _dispatch_async_redirect_invoke + 703
15 libdispatch.dylib 0x00007fff64b677e2 _dispatch_root_queue_drain + 326
16 libdispatch.dylib 0x00007fff64b67f22 _dispatch_worker_thread2 + 92
17 libsystem_pthread.dylib 0x00007fff64db36b6 _pthread_wqthread + 220
18 libsystem_pthread.dylib 0x00007fff64db2827 start_wqthread + 15

[saschaeggi]

+1

[saschaeggi]

I can successfully edit "DarkAquaAppearance.car" but not "SystemAppearance.car". ThemeEngine crashes when I want to edit SystemAppearance.

[grafikartes]

I tried with the update to 10.15.3 beta but it didn't solve.

[NLasagna]

Maybe same situation, just force closed. I don't know if it's helpful.

Thread 3 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000600003b48230 rcx: 0x00006000016d8060 rdx: 0x0000000000000002
rdi: 0x000001fe00001000 rsi: 0x0000000000000000 rbp: 0x0000700009431af0 rsp: 0x0000700009431ae8
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x00007fff9319e288 r11: 0x00007fff9319e280
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x00007fdb6a51df50 r15: 0x0000000000000000
rip: 0x00007fff31c92cff rfl: 0x0000000000010246 cr2: 0x000001fe00001000

[chris1111]

Same here it Crash

[ghost]

Editing previous comment because I tried something new and the previous rendition wasn't useful anyway:

When building from source you'll notice that ThemeEngine closes on opening SystemAppearance.car

Delete the line in the code or exclude it from being built and leave it in the existing code for future reference
if (facet_tree == NULL)

By building from source you can now do the following at the same time from the same ThemeEngine build... Assets.car can also be opened now.
Attached is a screenshot of a 10.15.3 DarkAppearance.car opened on Catalina 10.15.3
Attached is a screenshot of a 10.15.3 SystemAppearance.car opened on Catalina 10.15.3

[mrgooge]

I tried to compile, but get an error...
"Showing Recent Issues
There are no accounts registered with Xcode. Add your developer account to Xcode"
and
"
Showing Recent Issues

Build target ThemeEngine of project ThemeEngine with configuration Debug
error: No signing certificate "Mac Development" found: No "Mac Development" signing certificate matching team ID "3GD8ABJ22W" with a private key was found. (in target 'ThemeEngine' from project 'ThemeEngine')
error: There are no accounts registered with Xcode. Add your developer account to Xcode (in target 'ThemeEngine' from project 'ThemeEngine')"

@MUI68K anyway to get your build?

[ghost]

@MUI68K anyway to get your build?

Can you write an e-mail to [email protected]? I don't know if I can share directly here when I've changed actual code and not just building it directly from source with no change. I will provide a link that you can download from then.

[mihailsalari]

has somebody found a fix?

[ghost]

has somebody found a fix?

I don't know if my build of ThemeEngine is a fix, but it does work and as a far as being a fix - I fixed it for me and those who contacted me hasn't returned with a complaint that it doesn't work.

The code that I suggest cutting away is in the ThemeKit portion - but it's easiest to find when you build ThemeEngine from existing source and ThemeEngine then crashes upon opening SystemAppearance.car - the string I suggest is highlighted as being an error. That's how I initially played around with what I wrote earlier.

[grafikartes]

@ MUI68K,
thank you very much, works perfectly

[chris1111]

Please post here a working app

[ghost]

@chris1111 And everyone.

Link taken down because the latest fork of ThemeEngine available here
https://github.com/jslegendre/ThemeEngine/releases/tag/v1.0.0(114)

Works on macOS Catalina and macOS Big Sur too.

There's a description here https://github.com/jslegendre/ThemeEngine on how to edit and replace themes on Big Sur.

[chris1111]

@chris1111 And everyone.

Here's the link to the app that I wrote about above:
https://jumpshare.com/v/JzSfz8FEGwxqdPIXg23T+/ThemeEngine.zip

I'll leave it there for the time being.

Thanks its work 👍🏻

[mbert]

if (facet_tree == NULL)

You mean something like this?

    BOMTreeRef facet_tree = TKIvar(self.storage, BOMTreeRef, _facetKeysdb);
    //if (facet_tree == NULL)
        return;

So that means that the whole rest of the function should always be skipped? Why should it then be called at all?

[mbert]

Here's the link to the app that I wrote about above:
https://jumpshare.com/v/JzSfz8FEGwxqdPIXg23T+/ThemeEngine.zip

Thank you, I have tried it. It does not crash, but it shows some really weird behaviour: When editing a .car file, the list of resources in the middle column will always scroll to the bottom by itself when the window is in foreground. That makes it pretty useless for editing. Any idea why and how to fix it?

[ghost]

Here's the link to the app that I wrote about above:
https://jumpshare.com/v/JzSfz8FEGwxqdPIXg23T+/ThemeEngine.zip

Thank you, I have tried it. It does not crash, but it shows some really weird behaviour: When editing a .car file, the list of resources in the middle column will always scroll to the bottom by itself when the window is in foreground. That makes it pretty useless for editing. Any idea why and how to fix it?

I can't answer that - I have however looked into this issue as bugs me too.
One other developer has a push to ThemeEngine that relates to the scroll function and this particular behaviour - although on an older version of ThemeEngine.
I hope that Alex chimes in here soon to help a bit.

Initially I just wanted the application to function again by opening and saving .car files.
Also, it's not that useless as such for editing if you use the Group By = Scale to show the assets you only want to see and then search for your assets also. With that said, I think this app can get better, but I have no experience coding much of anything. It was by pure chance that I figured out how to not have the application crash all the time on certain .car files on macOS Catalina -> 10.15.3

[mbert]

One other developer has a push to ThemeEngine that relates to the scroll function and this particular behaviour - although on an older version of ThemeEngine.

Thank you, I have contacted the author of that patch to find out how exactly he fixed it (the PR is not mergable because it contains lots of other changes made by XCode that don't fit to what is in the repository).

Initially I just wanted the application to function again by opening and saving .car files.
Also, it's not that useless as such for editing if you use the Group By = Scale to show the assets you only want to see and then search for your assets also.

Yeah, that's how I was able to get productive, too. However it is still unnecessary trouble.

And I would still really like to find out what the underlying problem for the crash is.

[ghost]

Okay, so I've made the scrolling stop and added Affinity Photo export capability. Importing from Affinity Photo isn't happening at the moment.

One other developer has a push to ThemeEngine that relates to the scroll function and this particular behaviour - although on an older version of ThemeEngine.

Thank you, I have contacted the author of that patch to find out how exactly he fixed it (the PR is not mergable because it contains lots of other changes made by XCode that don't fit to what is in the repository).

Initially I just wanted the application to function again by opening and saving .car files.
Also, it's not that useless as such for editing if you use the Group By = Scale to show the assets you only want to see and then search for your assets also.

Yeah, that's how I was able to get productive, too. However it is still unnecessary trouble.

And I would still really like to find out what the underlying problem for the crash is.

Okay, so I've made the scrolling stop and added Affinity Photo export capability. Importing from Affinity Photo isn't happening at the moment.

Shoot me an email if you would like to take a look. I will explain what I did in a seperate comment if can backtrace the steps properly.

[mbert]

Okay, so I've made the scrolling stop and added Affinity Photo export capability. Importing from Affinity Photo isn't happening at the moment.

Shoot me an email if you would like to take a look. I will explain what I did in a seperate comment if can backtrace the steps properly.

Cool. Can you send me your patch? If you are not familiar with using git and creating pull requests, you might just (in a terminal window) run the following:
git diff >scrollstop.patch and send me the file scrollstop.patch, then I can try things out and create a pull request from the result?

[ghost]

If only that command worked.. I mean,,, I'm only greeted with the options for git diff

And, I am not all comfortable with using git - because I fuck up I think -

[mbert]

If only that command worked.. I mean,,, I'm only greeted with the options for git diff

You're inside the ThemeEngine directory cloned from github?

[ghost]

If only that command worked.. I mean,,, I'm only greeted with the options for git diff

You're inside the ThemeEngine directory cloned from github?

Yes,, I am inside the main cloned (copy) of the downloaded repository - not within the ThemeEngine folder within that folder... is that the trick?

[mbert]

Like this:

[mbert]

And then just attach that file to your next comment. I'll do the rest :)

[ghost]

I think I have problems because I'm working locally and not using the Github program. Can I import what I have done and import that to the Github app for better getting that command to work?

[ghost]

which one do I stay in? I don't think I'm dumb, but there's no content in the output because the diff fails
https://jumpshare.com/v/MdDwmenIsmi3aouTRKs3

https://jumpshare.com/v/jxKTKS3GI0ImasSVxFnS

[mbert]

Oh, I guess you downloaded the ZIP file rather than cloning the code in git?

If that is the case, you can proceed as follows.

From the github site, after clicking the green button for downloading, click the icon on the right:

Now, in a terminal window, in a directory different from the one where you have your code checked out, say in ~/Desktop, enter the command git clone followed by Cmd-V for pasting from the clipboard and then the return key.

After that you have a fresh copy of the git repo, say in ~/Desktop/ThemeEngine.

Now, still in the terminal, enter the directory where your work is, say in ~/src/ThemeEngine (use the directory where it really is). From that directory, enter: cp -r * ~/Desktop/ThemeEngine

This copies your changes into the fresh workspace.
Then, enter your fresh workspace: cd ~/Desktop/ThemeEngine. Now this should work:
git diff >noscroll.patch

I think your problem is simply that you did not clone a git workspace but downloaded a copy of the code without the git metadata instead (because that's what you get when you download the zip).

[mbert]

I won't be able to look into this before this evening. Take your time to check everything, based on my code. Then send me another patch if you find an issue to fix.

[ghost]

I won't be able to look into this before this evening. Take your time to check everything, based on my code. Then send me another patch if you find an issue to fix.

won't be necessary as your repo is functioning just fine - I forgot I was still using my hacky version of ThemeEngine. I just tried compiling yours 💯

Also, I thought of this - could one not include a /build folder within the repo that has the compiled version of that current repo already in there for the user to download from right here instead of having to make use of external links such as Google Drive and Jumpshare for the older revisions(in my case) ? I've seen other authors do this.

[mbert]

The github way would be to upload releases separately. I briefly thought about this yesterday, but then decided otherwise, because what we are doing here is totally inofficial. Also there is the signature issue, anything I produce will be without a trusted signature, so that people will not be able to run it straight away.

Before putting out a release I would really like to have some clarity who is in charge, or, better, whether @alexzielenski will eventually integrate PRs and create a release.

[mbert]

@MUI68K I have tried out the Affinity export feature. The import back into ThemeEngine is based on two AppleScript files which currently support the Adobe tools. I don't know the Adobe tools and hence cannot really guess how much of the code in the two scripts is more or less generic or specific to the Adobe software. Looks like we're going to need help here.

As it is now things are a bit subobtimal: I guess one should either make the choice (Affinity or Adobe) configurable or just plain stupid make both available through the menu. However, as mentioned, importing from Affinity is missing and should really be added.

[ghost]

The github way would be to upload releases separately. I briefly thought about this yesterday, but then decided otherwise, because what we are doing here is totally inofficial. Also there is the signature issue, anything I produce will be without a trusted signature, so that people will not be able to run it straight away.

Before putting out a release I would really like to have some clarity who is in charge, or, better, whether @alexzielenski will eventually integrate PRs and create a release.

Sure, I can see why this is the better approach - after all this isn't an official build - I guess we'll know soon enough how this all pans out.

@MUI68K I have tried out the Affinity export feature. The import back into ThemeEngine is based on two AppleScript files which currently support the Adobe tools. I don't know the Adobe tools and hence cannot really guess how much of the code in the two scripts is more or less generic or specific to the Adobe software. Looks like we're going to need help here.

As it is now things are a bit subobtimal: I guess one should either make the choice (Affinity or Adobe) configurable or just plain stupid make both available through the menu. However, as mentioned, importing from Affinity is missing and should really be added.

This I've also thought about - making the Send To Affinity - menuitem. I wouldn't know how to do that - the days before was just getting around that scroll issue and such - perhaps the change to using the original AppleScripts is on order, I've read that Serif does consider implementing - but the thread I read begain in 2018 or there abouts and is still ongoing. I have yet to properly figure this out.
And in all honesty, the Affinity Export thing was really just a test. I believe there should be a revert to the good old same state with Adobe scripting Send To and Receive From.

[mbert]

Thank you, @MUI68K! I have now followed your proposal and restored the old export/import functionality for the Adobe tools. The old binary is still downloadable, the new one can be downloaded here: https://drive.google.com/open?id=1PZzU7Bbo_-0Tc6LS8XUq9jYFb5dW_Kyd

The code in my repo (and in PR #54) now reflects the new binary. If somebody wants to play around with the Affinity import/export, here's the commit to start with:
affinity-rather-than-adobe-as.zip

[miladg69]

@chris1111 And everyone.
Here's the link to the app that I wrote about above:
https://jumpshare.com/v/JzSfz8FEGwxqdPIXg23T+/ThemeEngine.zip
I'll leave it there for the time being.

Thanks its work 👍🏻

You are amazing.

[ghost]

@mbert is there a way that one could in Xcode see what sort of stuff ThemeEngine outputs on a given change? It's in order to fix the misalignment of the Finder buttons for one. The version of ThemeEngine OS X El Capitan didn't have these issues where a change to the exact Finder toolbar button would make all buttons simply go POOF! Like they never wanted to be there in the first place.
I've wondered about if such an option existed in Xcode if I get the version of ThemeEngine for El Capitan and then perhaps try it on an actual installation of El Capitan. I think there has to be a way.
I have a feeling it concers a scale issue - I've seen that in the code when I was messing about. Just didn't look that much more into it.

[mbert]

Not quite understand whether I understand you correctly. Just in general terms:

There is an option for the target operating system version when you build ThemeEngine. This should be able to make the resulting binary compatible to older OSX versions. However the result will most certainly differ from a ThemeEngine version built with an older version of XCode on an older OSX version.

Also I guess you want something like a preview on the .car file produced, right? I think that is a functionality that one will need to create explicitly. And I'm afraid I don't have much of a clue of MacOS programming, so I won't be much of a help here.

[ghost]

Not quite understand whether I understand you correctly. Just in general terms:

There is an option for the target operating system version when you build ThemeEngine. This should be able to make the resulting binary compatible to older OSX versions. However the result will most certainly differ from a ThemeEngine version built with an older version of XCode on an older OSX version.

Also I guess you want something like a preview on the .car file produced, right? I think that is a functionality that one will need to create explicitly. And I'm afraid I don't have much of a clue of MacOS programming, so I won't be much of a help here.

Oh,, well. 'm going to have to try some things on my own - to see if they work or not.
I wasn't requesting a preview-window for this scenario. I might have mentioned it earlier, but for this question I was jsut curious about the back-end of it all and if it was at all possible to sneak-peek into the compiled .car file and see what happened with earlier .car files version newest and current .car files.
If I can replace - say, Tile with Scale(those entries I've seen) I might have a breakthrough. At least I will be clapping my hands 💯

I am used to so much replacing of .car files that I think I can replace a bit more-- poor SSD

[MoonPadUSer]

I know this is weird, but can someone upload the Mojave version of xcode, I can't download anymore since I downgraded but I can't download it from the apple page either because appearantly I am too young

[JuanPerezPerez1]

Theme Engine no longer receives from Photoshop. I don't know why it only receives if you run GUI
 (/Applications/ThemeEngine.app/Contents/MacOS/ThemeEngine)
 Can someone explain to me please?

[ghost]

Theme Engine no longer receives from Photoshop. I don't know why it only receives if you run GUI
 (/Applications/ThemeEngine.app/Contents/MacOS/ThemeEngine)
 Can someone explain to me please?

If you downloaded the most recent build - after the scrolling was fixed - you might also notice that that particular version was with an experimental Affinity export option. It never did receive from any Affinity application. I'm only mentioning this in case you have that version - because it broke the Photoshop "Send To" and "Receive From"

I would urge you to compile the latest that @mbert has put up on his fork of ThemeEngine as this was reverted to using Photoshop and Illustrator functions.

Otherwise, I'm unsure what is going on. It might not be that everything I personally fiddled with was reverted properly.

[JuanPerezPerez1]

Yes, I have tried with that git version and also with the two that he put in this chat. But they have the same problem with affinity and photoshop. They send the file to edit but ThemeEngine doesn't receive it later. When I open the app via GUI with terminal it works. I think it is a temporary remedy. I'm in Catalina 10.15.4 by the way.

[babang1da]

I fixed it #57

[staiboii]

@chris1111 And everyone.

Here's the link to the app that I wrote about above:
https://jumpshare.com/v/JzSfz8FEGwxqdPIXg23T+/ThemeEngine.zip

I'll leave it there for the time being.

appreciate if you can make the file still available man

[mbert]

@chris1111 And everyone.
Here's the link to the app that I wrote about above:
https://jumpshare.com/v/JzSfz8FEGwxqdPIXg23T+/ThemeEngine.zip
I'll leave it there for the time being.

appreciate if you can make the file still available man

I think you might use the file I placed for download in this comment: ThemeEngine-pr54a.zip.

[ghost]

@chris1111 And everyone.
Here's the link to the app that I wrote about above:
https://jumpshare.com/v/JzSfz8FEGwxqdPIXg23T+/ThemeEngine.zip
I'll leave it there for the time being.

appreciate if you can make the file still available man

Oh yeah, that's right - I forgot about that whole deal. I just assumed everyone was downloading the build from here: https://github.com/jslegendre/ThemeEngine/releases

[shiypc]

@chris1111 And everyone.

Here's the link to the app that I wrote about above:
https://jumpshare.com/v/JzSfz8FEGwxqdPIXg23T+/ThemeEngine.zip

I'll leave it there for the time being.

dead link :(

[ghost]

@chris1111 And everyone.
Here's the link to the app that I wrote about above:
https://jumpshare.com/v/JzSfz8FEGwxqdPIXg23T+/ThemeEngine.zip
I'll leave it there for the time being.

dead link :(

Edited my original posting.

There was no reason for me to keep it up seeing as the fixes issues that was most keeping ThemeEngine from opening and working on Catalina are now included in the link available through the URL below:
https://github.com/jslegendre/ThemeEngine/releases/tag/v1.0.0(114)

[chris1111]

Any news for Big Sur ?

[ghost]

Any news for Big Sur ?

Update.. you can open and edit themes on Big Sur with the ThemeEngine fork linked above.. and you can replace your edited files. However, you have to be ready for some extra unfamiliar steps when coming from Catalina and Mojave.

There's quite a lot going on with Big Sur, but I have been succesful in changing the trafficlights as a quick test; to this

[shiypc]

@chris1111 And everyone.
Here's the link to the app that I wrote about above:
https://jumpshare.com/v/JzSfz8FEGwxqdPIXg23T+/ThemeEngine.zip
I'll leave it there for the time being.

dead link :(

Edited my original posting.

There was no reason for me to keep it up seeing as the fixes issues that was most keeping ThemeEngine from opening and working on Catalina are now included in the link available through the URL below:
https://github.com/jslegendre/ThemeEngine/releases/tag/v1.0.0(114)

that url is dead too...
edit: it's not, GitHub seems to be screwing up the link, just copy paste and it works

[ghost]

@chris1111 And everyone.
Here's the link to the app that I wrote about above:
https://jumpshare.com/v/JzSfz8FEGwxqdPIXg23T+/ThemeEngine.zip
I'll leave it there for the time being.

dead link :(

Edited my original posting.
There was no reason for me to keep it up seeing as the fixes issues that was most keeping ThemeEngine from opening and working on Catalina are now included in the link available through the URL below:
https://github.com/jslegendre/ThemeEngine/releases/tag/v1.0.0(114)

that url is dead too...

Sorry about that -- I put the link inside URL code which isn't the correct way

[mbert]

There's quite a lot going on with Big Sur, but I have been succesful in changing the trafficlights as a quick test; to this

That looks really cool. Are you planning to release something?

Regarding Big Sur - since I only have my "productive" machine I am a bit scared. Longing to read a bit more about experience people have made with theming Big Sur, pitfalls etc.

[ghost]

There's quite a lot going on with Big Sur, but I have been succesful in changing the trafficlights as a quick test; to this

That looks really cool. Are you planning to release something?

Regarding Big Sur - since I only have my "productive" machine I am a bit scared. Longing to read a bit more about experience people have made with theming Big Sur, pitfalls etc.

It's early days still - I only have this one Mac too to work with - although I am not using it for anything productive as such.

edit No, I don't plan on releasing anything for Big Sur - it's too much of a task. It could be that theming Big Sur gets better in the future, but for now I am running on empty and despite having the desire to theme macOS - there's just not enough in it for me at this point.

[Panak252]

At the moment I'm using MacOS Monterey, it sucks without the gorgeous traffic lights. Same was when I used Big Sur. It's very unfortunate that you aren't going to release for Big Sur or Monterey. I've tried lots but nothing seems to work for me on Monterey. The only mod Was successful with was cDock beta for Monterey. I really hope you release for Big Sur or Monterey.
Thanks.

[borp99]

At the moment I'm using MacOS Monterey, it sucks without the gorgeous traffic lights. Same was when I used Big Sur. It's very unfortunate that you aren't going to release for Big Sur or Monterey. I've tried lots but nothing seems to work for me on Monterey. The only mod Was successful with was cDock beta for Monterey. I really hope you release for Big Sur or Monterey. Thanks.

You need to download a port done by Jeremy legendre (https://github.com/jslegendre/ThemeEngine). It works fine on Monterey and Big Sur.