My desktop application was also rejected because it has a subscription in-app purchase several months ago. So I was forced to switch to a non-consumable in-app purchase. But I ran into many desktop applications (Adobe Lightroom, CorelDRAW, Polarr Photo Editor...) with such when I was browsing applications with Mac App Store app several days ago. So I would ask them why they are allowed if your app is rejected with a subscription in-app purchase.
Tomato
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
User for
Post
Replies
Boosts
Views
Activity
If you don't hear their reply, you may consider filing an appeal. But you have to be careful when you do so. The appeal board used to be quite neutral, but things changed two to three years ago. These days, the appeal board is likely to take the side of the reviewer with or without reading your grieviance. If they rule against you, even when the reviewer is absolutely wrong, it's final. Basically, it's now an unreliable process. Sometimes, the reviewer changes their decision when they realize they are wrong if you give them 2 to 3 days.
That's excellent. Yes, it works. Thanks a lot.
Thanks. But I've removed an existing key equivalent for Command + H (Including Hide app).
If what I have islet showHomeMenuItem = NSMenuItem(title: "Show Home", action:#selector(showHome), keyEquivalent: "h"), then what appears on my status menu is Command + H. If what I have islet showHomeMenuItem = NSMenuItem(title: "Show Home", action:#selector(showHome), keyEquivalent: "H"), then what appears on my status menu is Command + Shift + H. And I'll get beeped if I press Command + Shift + H.
Claude,The following code shows sub view counts.class MainViewController: NSViewController {
@IBOutlet weak var displayView: NSView!
override func viewWillAppear() {
super.viewWillAppear()
print("No. of subviews before the display view shows up", displayView.subviews.count) // => 0
for sub in displayView.subviews {
sub.removeFromSuperview()
}
}
override func viewDidAppear() {
super.viewDidAppear()
for sub in displayView.subviews {
sub.removeFromSuperview()
}
print("No. of subviews after the display view shows up", displayView.subviews.count) // => 0
}
override func viewWillDisappear() {
super.viewWillDisappear()
print("No. of subviews right before the display view hides itself", displayView.subviews.count) // => 3
for sub in displayView.subviews {
sub.removeFromSuperview()
}
}
override func viewDidDisappear() {
super.viewDidDisappear()
print("No. of subviews after the display view hides itself", displayView.subviews.count) // => 0
}
}Initially, the memory consumption stays around 100 MB. After I hide the window and bring it back five times or so, it will go up to around 480 MB.
I don't necessarily mean to critisize how Apple, Inc. runs App Store and Mac App Store. But dealing with their reviewers is like playing the Russian roulette. Most reviewers find no problem if I give users one week of free trial and then validate their in app purchase status. But one reviewer now says no. Some reviewers seem to accept the idea that a desktop application can have a subscription-based IAP. Mine was rejected several months ago. It's very difficult for me to figure out what is acceptable and what is not.
Thanks, OOper. No, I don't insist on using tags. Could you give me some idea of how it could be done without the tag, please?
That's interesting. Thanks, OOper. I have to take a close look at what you have done.
Thank you, again, OOPer. That's an odd closure expression, which I have never seen in Swift.
Thank you, OOPer. The concern that I had with Text is that the string won't be necessarily placed inside the corresponding button. If I use your code, a small number will appear to the left of the corresponding button, not inside the corresponding button. I'm sorry if I failed to explain my needs initially.
Interestingly, there is a function called overlay.
Button("1") {
		
}
.overlay(Text("4").font(.footnote).foregroundColor(.blue).offset(x: -16, y: -16))
.buttonStyle(BorderlessButtonStyle())
.frame(width: 48, height: 48, alignment: .center)
.background(
		RoundedRectangle(cornerRadius: 2)
				.fill(Color.white)
				.shadow(color: Color.black.opacity(0.4), radius: 2, x: 0, y: 0)
)
Do I have to call it with onAppear like the following?
import SwiftUI
struct ContentView: View {
		@State private var eventPresented = false
		@State var fillColors: [Color] = Array(repeating: Color.white, count: 38)
		@State var buttonTitles: [String?] = Array(repeating: nil, count: 38)
		
		var body: some View {
				VStack {
						ZStack() {
								
						}.onAppear { makeButtons() }
						
						/* cal buttons */
						VStack(spacing: 0.0) {
								HStack(spacing: 0.0) {
										ForEach((0...6), id: \.self) {
												Button(buttonTitles[$0] ?? "") {
														eventPresented = true
												}
												.buttonStyle(BorderlessButtonStyle())
												.frame(width: 48, height: 48, alignment: .center)
												.background(RoundedRectangle(cornerRadius: 2)
																				.fill(fillColors[$0])
																				.shadow(color: Color.black.opacity(0.4), radius: 2, x: 0, y: 0)
												)
										}
								}
								...
								...
								...
								HStack(alignment: .top, spacing: 0.0) {
										ForEach((35...36), id: \.self) {
												Button(buttonTitles[$0] ?? "") {
														
												}
												.buttonStyle(BorderlessButtonStyle())
												.frame(width: 48, height: 48, alignment: .center)
												.background(RoundedRectangle(cornerRadius: 2)
																				.fill(fillColors[$0])
																				.shadow(color: Color.black.opacity(0.4), radius: 2, x: 0, y: 0)
												)
										}
								}
								.frame(width: 336.0, height: 48.0, alignment: .leading)
						}
				}.frame(minWidth: 370, idealWidth: 370, maxWidth: 370, minHeight: 420, idealHeight: 420, maxHeight: 420, alignment: .top)
		}
		
		func makeButtons() {
				buttonTitles.removeAll()
				for i in 0..<38 {
						buttonTitles.append(String(i + 1))
				}
				fillColors.removeAll()
				for _ in 0..<2 {
						fillColors.append(Color.clear)
				}
				for _ in 0..<36 {
						fillColors.append(Color.white)
				}
		}
}
What is important is that do you want to invoke makeButtons at each time when the ZStack appears? In fact, the answer is Yes, OOPer. Thanks for asking the question.
Thank you, workingdogintokyo and OOPer. This time, I choose my own answer as a solution.