I do not use autolayout. My app is incredibly dynamic, in that users can drag fields onto a canvas to create forms. Therefore, I have developed my own routines to render my xibs on any device in either portrait or landscape. To do this, I make sure the Use Autolayout is not checked for the xib's view in the file inspector. In fact none of the boxes are checked (trait variations, safe area, etc). However, I continue to get constraint errors. Is this just a bug. My code works perfectly but it is quite annoying to get the plethora of warnings in the output window. This just started in the last release or two. I am using XCode 9.2 with a deployment target of iOS 11.
Related
I am having problems using the Ikonli icon packs. I am creating FontIcon objects and then using those to set the graphics on buttons. Icons taken from the FontAwesome5 pack work great. Icons taken from the Material2 pack seem to shift somehow - for example, I try to get mdal-6_ft_apart but what actually gets displayed is mdal-loyalty. And no matter which Icon I load from MaterialDesign2, all I see is an empty box.
I'm running this through Eclipse, and everything looks fine when stepping through with the debugger. This is the value of the button graphic:
ObjectProperty [bean: mdal-6_ft_apart:15:0xffffffff, name: iconCode, value: MDAL_6_FT_APART]
and yet, on the screen, it's something completely different.
This is a Maven project using OpenJDK 16 and JavaFX 16. I've tried loading just a single icon pack instead of all 3, but no difference. Also, there are never any errors retrieving the icons. The ServiceProviders are all found, and the icons are available.
I made a small Hello World program and everything runs fine, so it's definitely an issue with my program and not the library. But I have no idea what the problem is, and I've been staring at this for almost 2 hours. Has anyone come across this before? I'd appreciate any help, because I'm out of ideas.
Answering this myself in case it saves someone else some time. I was installing the Ikonli library in order to replace the FontAwesomeFX library that is no longer available. I had gotten partway through replacing the icons when I ran the app in order to check the progress, and that's when I saw the errors.
The problem turned out to be an interference between the two libraries - FontAwesomeFX was throwing of Ikonli. The icon shift didn't actually occur until the code displayed a FontAwesomeFX icon, which made it seem a little random depending on the order I would open the dialogs when testing. I'm assuming an issue with the Service Handlers, though I'm not positive because I stopped troubleshooting once I realized the problem and just finished the replacement.
Once I stopped displaying FontAwesomeFX icons and the dependency was removed, Ikonli worked fine.
I might be missing something super obvious, but running an app compiled against watchOS 5 on the Apple Watch Series 4 simulator always results in the contentSafeAreaInsets and systemMinimumLayoutMargins returning zero (zero for left/right/top/bottom).
I've tried creating a sample project in case it was something weird in my app, but no luck.
The docs state:
The system’s built-in containers and controls automatically use the
content-safe area insets; however, if you build a custom user
interface with SpriteKit or SceneKit, you should check the
contentSafeAreaInsets and systemMinimumLayoutMargins, and lay out your
interface accordingly.
So I've tried adding a SceneKit scene to the Storyboard but that's had no effect, even when launching all permutations of the "full screen" and "fixed to screen edges" options enabled and disabled:
Edit: If I background and foreground the app the values are reported successfully, which makes me believe this could be a bug in watchOS if there's no workaround. It seems unreasonable to expect a user to background and foreground an app to get the correct behaviour.
On a project I work on, using Python3 + PySide, I try to print a popup-message as some sort of notification.
This popup needs to be on top of everything, this includes fullscreen applications like games or browsers. And that's the point that does not work. It works fine for all windows on my Desktop, normal windows, maximized, but as soon as there is a fullscreen application or a borderless window ("pseudo fullscreen") the popup is created, but "behind" the fullscreen app.
I already use self.setWindowFlags(QtCore.Qt.FramelessWindowHint | QtCore.Qt.WindowStaysOnTopHint) but this flag does get ignored by other fullscreen apps.
How do I fix this? Also without giving focus to the popup.
It is just there to present information, and it is not good when your window looses focus while playing a game.
My code can be found here: https://github.com/GosuSan/PyECM
additional Info:
- my project aims to be cross-platform, so I need a platform-independend solution
- I am running linux, without having a windows machine atm,
so I can't test stuff there.
If you need any more info, let me know!
Edit:
It seems that PySide.QtGui.QSystemTrayIcon.showMessage does what I want, it works on fullscreen as well as on borderless-windows. So I will try to either find out how those messages are displayed on top, or just use them, not sure for now.
What is happening to my app in Xcode 7 / iOS 9?
The whole screen looks condensed, as if an iPhone 4S app is displaying on an iPhone 6. It looks normal in the iPhone 4S simulator.
I thought it was a problem with the auto layout constraints in the main storyboard, so I eventually deleted everything apart from the root view in the root view controller (blue screen), and there's still a problem with it.
I tried enabling size classes, thinking that this was the problem due to previously being disabled, but the result was the same.
Is anyone else getting this problem in their existing apps running in iOS 9?
Target>General>Launch Image Source>use asset
it will create new asset named BrandAsset, place your launch images over here. Create LaunchScreen.storyboard if already not existing and select it to Target>General>Launch Screen File.
Thanks for the answers. They pointed me in the right direction, as I wasn't aware it was anything to do with the launch screen.
I found out I had no LaunchScreen.storyboard file. Digging around in the docs led me onto this:
New projects are created with a launch screen storyboard file called
LaunchScreen.storyboard. Alternately, you can create a new launch
screen file using File > New, selecting the User Interface category,
and choosing a file type of Launch Screen.
It was weird that I had to do this, as I only started developing this app in iOS 8, and apparently this was a change in iOS 8. But with iOS 9 Apple are obviously getting more aggressive with deprecating incorrectly set up projects, and the consequences were that it was bug to my app.
The positive I guess, is that all of this forced me to at least create a launch image instead of having nothing.
We have an application running flex sdk 4.5 and have recently encountered an issue with textInput fields which we have not been able to reproduce on our end for the better part of a month now.
Here are the symptoms:
Users opens an input form which contains several input fields (combo boxes, calendars, text inputs, etc)
User clicks inside a text field
Users types (obviously!)
** Nothing appears in the text input - we have validators on some of these fields and they do kick in properly (ie. user sees red box around textInput disappearing)
User moves cursor outside of text input field and text appears
Give or take, this is the test case we've been provided. We have been unable to reproduce this and I'm reaching out to see if anybody has heard of issues like this in the past.
They are running our flex application in the following environment:
Windows XP SP3
IE 7.0.5730.13 (locale = en-gb)
Flash Player 10.3.181.14
Upgrading either of these components is not an option. Installing the flash player debugger is not an option either.
Now we've setup a pc exactly the same way as they have on their end and still haven't reproduced. So we're really stuck at this point :)
Any suggestion is greatly appreciated. I'll provide any additional info needed.
-Marc
Feb. 2nd 2012 - Update
As I noted in my comment reply to shaun, it seems our customer was more or less precise in their description of the issue. We ran a webex session with them this morning and actually saw the issues first hand.
Here's what happens:
- User loads our application via its url
- User is able to input data and pretty much do any function for a 'random' time period
- All of a sudden, the issues start (there are more symptoms than just the one I originally mentioned):
1. Users type in text input fields and they won't see the text appear until they move the cursor out of / into any other component (could be entering an hbox, exiting a text input field, etc)
2. Combo boxes behave more or less the same. They can drop them down, but then the mouse wheel no longer refreshes the list. It actually scrolls in the background, but until the user moves the mouse, the list does not refresh
3. We also communicate between the server and client via an amf channel. The events make it to the client, but again, they won't see the screen refresh until they move their cursor.
So basically, the application still seems to work, but the screen is no longer refreshing. Could it be something to do with an invalidate / update of the display list that doesn't kick in? We'd like to get them to install the debugger version of FP, but that doesn't seem to be an option.
Another thing to keep in mind: they have a VERY bad internet connection. They average around 1-1.5mbps (megabits) which is enough for our app, but I just thought I'd let you know.
We learned that they also use a Citrix presentation layer to deploy IE 7 to the end users. We've received confirmation from the end user that even if they launch IE on their workstation (not through citrix), they get the issue also.
Another note is that we've seen no errors in our web server, jboss or application logs...
So that's the update I've got... anyone have more thoughts on this? We've more or less discarded the fonts being an issue at this point since the issue affects more than just 'fonts'. Is everything on the screen not updating anymore.