Jump to content
485 posts in this topic

Recommended Posts

I don't see these 2 new ones attributed in misc, maybe it's still early?!

 

0x0100 — OC_ATTR_USE_REVERSED_UI

 

0x0200 — OC_ATTR_REDUCE_MOTION

 

However, I would say that the problems of beta 14.4 are enough and advanced :hysterical:

  • Haha 2

@Baio77 has an updated fork of OCAT up to OC 0.9.8 but it has to be compiled (no release), which is beyond my knowledge.

There is a Pull Request in progress.

 

Edited by miliuco
1 hour ago, miliuco said:

@Baio77 has an updated fork of OCAT up to OC 0.9.8 but it has to be compiled (no release), which is beyond my knowledge.

There is a Pull Request in progress.

 

https://github.com/Baio1977/OCAuxiliaryTools/actions/runs/7791632241

 

Screenshot2024-02-06alle00_47_03.png.8c9d374ef6b00cea35bac99f91b6756c.png

  • Like 3

 

Clarification: after a major OCAT update it is recommended to remove the temporary files that the application itself generates. By doing so you will have access to the files actually contained in the most updated version of OCAT. However, the temporary files folder contains traces of previous versions of OCAT.
 

image.png.c263c9b513f02836badfbafa0ee70cfc.png

 

The Actions from the official repository fill out my pull request

image.png.e78fa9eee012cdcae12b889dc665a861.png

 

Edited by Baio77
  • Like 4
41 minutes ago, Baio77 said:

 

Clarification: after a major OCAT update it is recommended to remove the temporary files that the application itself generates. By doing so you will have access to the files actually contained in the most updated version of OCAT. However, the temporary files folder contains traces of previous versions of OCAT.
 

image.png.c263c9b513f02836badfbafa0ee70cfc.png

 

The Actions from the official repository fill out my pull request

image.png.e78fa9eee012cdcae12b889dc665a861.png

 

Apparently my fork need update...

I've updated my fork.

Now OC 0.9.8 is supported.

 

Downloads:

https://github.com/andyvand/OCAuxiliaryTools/releases/tag/20240002-baio

 

OCAT_Win.png

OCAT_Mac.png

Edited by Andy Vandijck
  • Like 3
39 minutes ago, Andy Vandijck said:

I've updated my fork.

Now OC 0.9.8 is supported.

 

Downloads:

https://github.com/andyvand/OCAuxiliaryTools/releases/tag/20240002-baio

 

OCAT_Win.png

OCAT_Mac.png

Hey Andy,

I use Mojave 10.14.6 and Catalina 10.15.7 on my laptop. I don't install every update. Is it possible for you to make the app backward compatible? Currently, I receive this message:

"You cannot use this version of the 'OCAuxiliaryTools' program with this version of macOS. Your computer has macOS 10.14.6 installed. The program requires macOS 11.0 or later"

22 minutes ago, spakk said:

Hey Andy,

I use Mojave 10.14.6 and Catalina 10.15.7 on my laptop. I don't install every update. Is it possible for you to make the app backward compatible? Currently, I receive this message:

"You cannot use this version of the 'OCAuxiliaryTools' program with this version of macOS. Your computer has macOS 10.14.6 installed. The program requires macOS 11.0 or later"

I'm gonna make the 10.13 legacy target if possible.

EDIT: Qt-6.X does not support 10.13, 10.15 minimum, building Qt for 10.15...

EDIT2: Qt 6.6.1 for 10.15 has been built, building OCAT...

Edited by Andy Vandijck
  • Like 3
27 minutes ago, spakk said:

Hey Andy,

I use Mojave 10.14.6 and Catalina 10.15.7 on my laptop. I don't install every update. Is it possible for you to make the app backward compatible? Currently, I receive this message:

"You cannot use this version of the 'OCAuxiliaryTools' program with this version of macOS. Your computer has macOS 10.14.6 installed. The program requires macOS 11.0 or later"

10.15 version is built.

 

https://github.com/andyvand/OCAuxiliaryTools/releases/download/20240002-baio/OCAT_Mac10.15.dmg

 

  • Like 3

no offense to anyone guys, actually thanks for your contribution but I'm waiting for the final merge from ic005k... there's a risk of causing a bit of confusion like this (my opinion) especially inexperienced users

  • Like 2
17 hours ago, eSaF said:

I deleted this New version and returned to the original OCAT.

I noticed a quirk I didn't like that is missing from the original.

With the original whenever I open my config.plist, I have two choices of Editors, either PlistEdit Pro or OCAT with OCAT presenting it self as the Default.

This New version does not (as shown in the pic). Maybe it's me or my machine but I don't like it, so I returned to what works for me.

Screenshot 2024-02-05 at 20.49.18.png

Fixed this in a new build.

<array>
	<dict>
		<key>CFBundleTypeExtensions</key>
		<array>
			<string>plist</string>
		</array>
		<key>CFBundleTypeIconFile</key>
		<string>Icon.icns</string>
		<key>CFBundleTypeName</key>
		<string>OCAT Document</string>
		<key>CFBundleTypeRole</key>
		<string>Editor</string>
		<key>LSHandlerRank</key>
		<string>Owner</string>
		<key>LSItemContentTypes</key>
		<array>
			<string>com.apple.property-list</string>
		</array>
		<key>NSDocumentClass</key>
		<string>Document</string>
	</dict>
</array>

This was missing...

Edited by Andy Vandijck
  • Like 1

@pkdesign

 

Forks are a fundamental part of GitHub. GitHub is a place to share your code but also (very importan) a place to collaborate on someone else's code.


You publish your code >> I think I can improve it in some way >> I create a fork of your GitHub repository that is a synchronized copy >> I work on the fork and make the changes that I consider useful >> Then I create a Pull Request that is seen in your repository with the proposed changes >> You review the Pull Request and decide if you accept the changes (you merge my code with yours, your repository with the updated code now has 2 collaborators, you and me) or If you reject them and inform me of the reason or if you ask me for some other change so that you approve it >> In the end, 2 unknown people, far from each other, collaborate on the original code in a selfless way that is at the same time very simple.


It may also be that I create a fork of your code to make it known to my followers or the people who access my GitHub.


In short, forks are the way to collaborate and often improve code from GitHub repositories.

 

@ic005k can improve his app merging pull requests or ignore them. OCAT has more than 2 dozen forks which gives an idea of the interest this app generates in the community. This is also a positive indicator for the developer.

  • Like 2

I agree with you but in my opinion all this should remain on github to avoid creating confusion for users I'm welcome if @ic005k then accept the various proposals...there's no point in publishing the artefacts

.... I don't know if I explained myself

Edited by Antonuccio
  • Like 2

You missed that ic005k written his sources for Qt5 framework while Andy remaked them to Qt6 framework. They can't be merged they are different very much.

But they work similar. 

  • Like 2
2 hours ago, Slice said:

You missed that ic005k written his sources for Qt5 framework while Andy remaked them to Qt6 framework. They can't be merged they are different very much.

But they work similar. 

They can be merged.

I kept Qt 5 compatibility.

I do a version check to accomplish this.

I also merged @Baio77 fork.

  • Like 3

https://github.com/ic005k/OCAuxiliaryTools/actions Fix ocvalidate 0.9.8.

If you can test that it works, remember before starting a new OCAT it is essential to remove the temporary files of the previously installed version.

THANK YOU

Edited by Baio77
On 2/8/2024 at 3:11 PM, Andy Vandijck said:

I've built a 10.13 version too.

I used Qt 6.0.4.

https://github.com/andyvand/OCAuxiliaryTools/releases/download/20240002-baio/OCAT_Mac10.13.dmg

I couldn't open the DMG file; the following error message was displayed: 'OCAT_Mac10.13.dmg' - Resource is busy. Can someone please upload the app as a ZIP file?

 

3 minutes ago, spakk said:

I couldn't open the DMG file; the following error message was displayed: 'OCAT_Mac10.13.dmg' - Resource is busy. Can someone please upload the app as a ZIP file?

here you go

OCAuxiliaryTools.zip

  • Like 1
11 minutes ago, chris1111 said:

Thank you very much, Chris. However, the app won't launch. After a double-click, the app briefly opens and immediately shuts down. Has anyone been able to open and use this Legacy app for MacOS from their Hackintosh running High Sierra 10.13? I've attempted to open the app on MacOS Mojave 10.14.6, but unfortunately, it didn't work.

×
×
  • Create New...