Post not yet marked as solved
Hello, I am trying to create a map for an event using MKTileOverlay.
I am creating a map for an event using MKTileOverlay. When the map is enlarged beyond a certain size, the MKTileOverlay is not displayed.
Since I plan to convert the SVG and display it, I think I can draw it using MKCircle and other methods by converting it well, but considering the amount of work and clean rounded corners, I would like to draw it using MKTileOverlay if possible.
Is there any way to solve this problem?
Post not yet marked as solved
I saw the Design great Widget. The calendar widget in dark mode, featured at 14:10, was with a gray background, but the current beta version of the is black. Is this a bug? Black background color in dark mode (e.g., calendar, screen time) and gray background color (e.g. (e.g., music, reminders), and since I don't know which one is correct, I have to unify I would like to have it.
Post not yet marked as solved
I saw the Design great Widget. The calendar widget in dark mode, featured at 14:10, was with a gray background, but the current beta version of the is black. Is this a bug? Black background color in dark mode (e.g., calendar, screen time) and gray background color (e.g. (e.g., music, reminders), and since I don't know which one is correct, I have to unify I would like to have it.
I created a *.keylayout usingthis document as a guide.Here is a concise version of my *.keylayout (full). If you would like to try it, copy it and save it to `~/Library/Keyboard Layouts/` under the name `test.keylayout`. Then add it in input source of Keyboard of System Preference.Now I have two problems.ANSI to JIS inherits the `keyMap`, but no other inheritance works.Cannot type an Entity reference such as `<`.Details are the following.ANSI to JIS inherits the `keyMap`, but no other inheritance works.The documentation also says "Virtual key codes not overridden are copied from the base element." I thought that `baseMapSet` should not be the same, so I tried to create `baseMapSet` for each index, but it didn't work.Of course, it would work if I wrote everything without using baseMap, but I don't want to do it because it's too weak and hard to change.Cannot type an Entity reference such as `<`.It worked in the older version. It does not work even if you remove `baseMap`.How do I make a working *.keylayout?
Post not yet marked as solved
In recent years, there is a close button in the upper right corner of iOS. For example, the half modal sheet of Map has the title on the left, so you may not be able to do anything about it. However, there are times when you can put the close button on the left side, but the close button is on the right side.
For example, the new iOS 14 feature, App Clips, is also a new feature in iOS 14, and you'll see a close button in the top right corner. Is "close" a primary action? I know of an even worse example: even in Apple Books, rather than having a close button in the upper right corner but surprisingly, the buy button, which should be a primary action, is on the left side. It's not even consistent with the App Store.
The examples are endless, such as Messages and Shortcuts' Details sheets also has a Done button in the upper right corner. These are essentially modeless operations, so you can add the X button in the upper left corner that I feel like.
Oops, speaking of Shortcuts, this Details sheet doesn't have a cancel button. Despite this, it's a modal sheet. What is the purpose of this? Automation is also full of surprises. Each cell looks like a NavigationLink, but you can actually make the cell When I press it, the sheet comes up. Is there a reason it has to be modal? The screen to edit shortcuts also have a problem. The "..." button is in the upper right corner, and it is in that position, so it seems to be a primary action. But the close button is taking up the right side of the Navigation Bar, so I can't see it when I scroll down. it should be fine as long as it's like Mail.
The close button is in the upper left corner. A few years ago I thought this was a principle of the Apple’s platforms, but it seems to be different on iOS these days. Has the design philosophy changed? If changed, I wanna hear you explain it. If it hasn't changed (and this is my hope), before iOS 14 sees the light of day, please fix as many mistakes as you can. I can only tell you wrong design In iOS , but I wanna help you.
MasasaM.