I am working on 3 windows applications which are built in VB. Last week I got an OS (windows 10) update which updates the build (version 1909 Build 18363.1500) of the system. After this update the scroll bars of all 3 applications in the Datagrid got invisible.
I tried to upgrade the framework to higher version but still it is not working.
This is likely the result of Microsoft update KB5001337 being installed in Windows 10 1909. See April 13, 2021—KB5001337 (OS Build 18363.1500), the "Known issues in this update" portion of that page.
According to that 'known issue', "Microsoft is working on a resolution and will provide an update in an upcoming release."
Until Microsoft fixes this, from other reports on the 'net about this problem, uninstalling KB5001337 will restore the scroll bars.
Running a later Windows release (eg, 20H2) does not seem to incur the problem, so another option is to upgrade Windows.
Edit - Workaround
(credit to Jimi for pointing this out in a comment)
At least for Winform impacted applications, it appears that specifying the dependency on v6 of the Common Controls library will bring the scroll bars back.
In the application manifest, add (or uncomment) the dependency for Commmon Controls. Should look at least similar to this:
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="*"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
Related
I upgraded to Catalina and can no longer open one of my apps (Typinator). I'm getting the error below.
I tried a few solutions I found online:
right click while holding ctrl + click
change accessibility settings to allow for Typinator
Any other ideas?
It's always worth it to visit the manufacturer's site
Important Notification for Typinator users switching to Catalina.
Typinator versions older than 8.2 do not work with Catalina and will refuse to launch. To ensure smooth transition to macOS Catalina, we therefore strongly recommend updating Typinator to version 8.2 before you install macOS Catalina on your computer.
For more information, please see our compatibility page
Edit: Probable Bug. Seeking fix or workaround…
How can I get the system’s text styles to be available in the interface builder when using Xcode 11?
I just started using Xcode 11 this week. In the interface builder (storyboard mode), when I go to assign a dynamic type text style to a Label or Button, using the Font -> Style pop-up, all the text styles are missing from the popup menu.
I do have the Dynamic Type “Automatically Adjusts Font” checkbox checked, as well.
I’m not sure if this is a bug, an intentional change I can’t find documentation for, or something else.
The expected behaviour is described in Apple’s developer documentation “Scaling Fonts Automatically”. Specifically, in the “Configuring Text Styles Using Interface Builder” section.
Further exploration: I’ve tried it with new projects, old projects (from Xcode 10), projects targeting iOS 12.2 and 13.1. All had the same problem of no text styles in the popup menu.
I experience the same problem when upgrading from Xcode 11.0 to Xcode 11.1 or 11.2 beta 2:
Xcode 11.0:
Xcode 11.1:
I also filed a bug report (FB7415999) with Apple and also opened an issue with them.
**My curren solution at the moment is a downgrade to Xcode 11.0 for UI development and a parallel install of Xcode 11.2 beta for on device runs **
This is probably a bug in Xcode 11.1. I ran into the same thing and filed a bug with Apple (FB7368959). A colleague running Xcode 11.1 on Catalina did not have the same problem, nor did another running Xcode 11.1 on Mojave.
Here is a workaround that got me back on track: I opened the problematic project in both Xcode 10.3 and 11.2 beta. In both, the dynamic type styles were available in IB. I didn't change anything, but reverted to Xcode 11.1, and now the styles are there, too. Hopefully this works for Grant and anyone else that runs into this annoyance.
Edit Mar. 17, 2020: This problem has reoccurred for me on Xcode 11.3.1. It seemed to happen with a specific project, and the problem spread to a second machine as soon as I opened that project. My workaround didn't help when I opened the project in 11.4 beta 3.
Apple announced the Xcode 5 Developer Preview today and I want to try it.
But before I download this, I want to know that what happen with my current version of Xcode (version 4.6.2)?
Will the Xcode 5 Developer Preview install as a different application or it will remove the old version? Will some common tools collide, like the command line tools?
The Xcode 5 developer preview comes as a normal app DMG (not with the usual packager/installer) and has a different name.
So essentially, you download it, open a DMG, then pull to the Applications folder and thence have two Xcodes there (the old and the new one called Xcode5-DP). It even comes with a slightly different icon (red badge across a corner) and the intro screen is different too, so there is very little chance of confusing them.
I already did that today (and a colleague also).
Now that xcode 5 has reached the first official release and is no longer in beta, you have to do ONE of the following if you wish to keep BOTH versions.
Run the dmg of the new version you download from developer.apple.com. Drag the app to applications, and when asked to overwrite click KEEP BOTH. This will rename the existing app to xcode 2 I believe.
Select your existing xcode 4 in applications. Rename it to xcode4 or whatever. Now you can drag in the new version without overwriting the existing one.
Drag the new xcode to someplace other than applications. Rename it and then drag it into applications.
I personally favour option 2, since going forward we'll be using xcode 5 and it's helpful if it retains the default name from the get go for easy updating.
BTW, if you do have more than one xcode installed expect the mac app store to report that you need to do an update. Probably best to install it by downloading it from the developer portal if this sort of thing bugs you.
Xcode 5 preview works fine with Xcode 4.6.2 or any other Xcode, It has different icon and it runs from its .dmg file (no install).
Pay attention you cannot submit an app with Xcode 5, So keep the old Xcode till Apple would release the stable version of Xcode 5.
Short answer: Dont replace XCode 4!
If you plan to deploy some app to appstore, you can't do it using Xcode 5 at this moment.
The best way is download the Xcode 5 version, unpack it and run the app on different folder (not application folder). You will stay with Xcode 4, and can run Xcode 5 separated (You don't need to 'install' xcode 5).
We have an application that integrates with different programs (among which is the Preview.app) using accessibility. We use the AXUIElementSetAttributeValue function to programmatically select some text in a PDF document using the kAXSelectedTextRangeAttribute. This used to work fine but suddenly stopped on my Mac (nothing seems to happend). My co-worker doesn't have the issue so after trying to figure out the difference I remembered that I had just updated to OS X 10.8.4 while he hasn't. I then read about this update and among the features and fixes was the following:
Improves VoiceOver compatibility with text in PDF documents
This indicates to me that they have fiddled with the area where I am having the issue. My question is now weather this is simply a bug or if it is by design. In the case of the latter, what am I supposed to use in stead?
PS. We tried also setting the selection range using the Accessibility Inspector found under Developer tools in Xcode and it works fine in 10.8.2 but not in 10.8.4, which further indicates that this might be a bug.
This is indeed a bug. I just installed the developer preview of OS X 10.8.5 and the issue has been resolved here. In the change-log it also says that some of the changes in this version regard "PDF viewing and Accessibility".
I'm trying to get a copy of the iOS simulator that includes an iPad retina display. I followed the advice on this thread, downloading the latest copy of Xcode: https://developer.apple.com/xcode/
However, having downloaded that, it didn't actually update the simulator, which still lacks support for the retina display for iPad. Am I missing something?
OK, I've found the answer, and considering there is zero documentation, I'm amazed that anyone else was ever able to find the simulator. Here's how you get there:
Right-click on the Xcode file and select Show Package Contents
Go Contents --> Developer --> Platforms --> iPhoneSimulator.platform
--> Developer --> Applications --> iOS Simulator
Intuitive, huh?
Why Apple decided to bury what is arguably the most used tool in the entire iOS SDK is something I will probably never know.