I have a working JavaFX app running on windows 10.
I would like to use the touch-keyboard in a similar to MSDN user input scope to change the touch keyboard
HOWEVER there is no way to interact with it. All textfieeds open the Default keyboard.
I would like to find the closest to JavaFX as possible solution.
Things I have tries so far:
Tried to use the WM_MESSAGE to trick the OS, see Here. This is a messy workaround that does not work on windows 10.
Encapsulating the WM_MESSAGE or InputScope object in an executable, and calling it from JNI only creates a one-way transition from app to keyboard. it will not suffice.
Using a custom keyboard or the JAvaFX touch keyboard (see here is not a valid solution as these keyboards look a bit messy, and they require some twirking we already know exist.
set-numeric-layout-for-windows-onscreen-keyboard-programmatically not working.
activating-touch-enabled-controls-in-javafx is irrelevant.
I am using QT 5.7.0 on Arch Linux. I am a beginner at Qt and hence I am watching some tutorial videos.
What I find odd and annoying is that the person in video is using the same main version but gets all the Intellisense auto-complete feature working perfectly. But on the other hand , mine is not giving options to all the Options.
For example,
When he types "SIGNAL", he gets a lot of drop-down options to choose from. But I don't .
On my Qt:
This does not happen everywhere. In some functions or variables, I do get the drop-down . But I don't get it for some set of keywords : like SIGNAL,SLOT etc..
Even when I get the options, its too few compared to the Video.
I have enabled this feature in my settings :
Please help me solve this problem. I really need this feature as I am learning Qt.
I'm looking to customize a bit of the atom interface, I'm wondering though, is there a way to "inspect element" or similar so I can know what classes are on there. I haven't been able to find anything, but it's new and it might just not be well documented yet.
Does anyone know how to know what the different classes are of the elements on the interface? or a way to get the "html"?
Sure! First of all, if you launch Atom in development mode (with the -d argument on the command line), you'll actually have an "Inspect Element" in your context menu that does exactly what you describe. Even outside of development mode, though, just open the developer console with cmd-option-i (or View -> Developer -> Toggle Developer Tools from the menu) and click on the "Elements" tab to view the full DOM:
You might also find the Styleguide useful, since it documents the built-in CSS classes and interface elements. Launch it from the command palette with Styleguide: Show.
I have been struggling with Xcode 3, and decided to jump directly to Xcode 4.
However, a big problem is that there is very little support like articles, videos, and projects I can use as templates.
Does there exist support like this at all?
Can I use Xcode 3 projects as templates?
Would it be easy to work from Xcode 3 tutorials?
I have now been using it for one day. Some things in the interface designer are quite different. For example, I can't get to subviews in the tab bar control (but mostly I manage, and can follow examples).
Thanks.
I'm doing the same thing. Xcode 4 is in pre-release, so there's not much in the way of tutorials while the tools are in a semi-NDA limbo and could be changed significantly before final release.
I highly recommend reading tutorials (I'm working my way through Aaron Hillegass' books on iPhone and OSX development) that use Xcode 3, and allowing extra time for learning where to map across to the new version.
Xcode 4 is much better organised, so it can be annoying but not impossible to find what you are looking for fairly quickly.
Resources you should go to first:
WWDC10 sessions 307, 308 and 315:
Introducing Xcode 4,
Developing your app with Xcode 4, and
Using Interface Builder in Xcode 4.
Access these through the developer portal. They are the definitive Apple guide to the new design and workflow.
In the Xcode 4 Help menu, the Xcode 4 Transition guide is the second choice. I skimmed it, then kept coming back to dive into topics when they came up.
Xcode 4, despite being "released", is an absolute disaster. I would wait for at least a couple of updates (beyond 4.01) before moving to it.
Basic functionality is severely broken. Breakpoints, syntax highlighting, basic functionality in the Interface Builder IU... I don't even know where to begin.
The document management, which was the towering defect of Xcode's design up to this point, has been changed but sadly not fixed. It might even be worse.
At first I had some good impressions. Early notes:
More-sensible defaults for debugging hotkeys.
There's now "Close project" in the File menu!
You can finally set up sounds for lots of build & search events, with a GUI. Nice.
There's a drop-down that shows files that are associated with the one you're editing. This might be useful, but any convenience this might add is ruined by the fact that there's no quick "counterpart" button like there used to be. You have to dig through a menu to go from header to source or vice versa.
Tabs are upside down, extending off the toolbar (WTF). Also, the "X" to close indicator is missing from each tab unless you roll over the tab. This kind of Easter-egg UI hides information from the user and should be abolished.
The tabs don't work well for a couple of reasons. First, there can be two editing panes under one tab with different documents; the tab only shows the name of one of them. You also can't move documents between panes, which you often want to do when referring to different objects and interfaces. Visual Studio solves both of those problems easily by having separate tab groups above each editing pane and letting you drag documents between the two groups.
A second editing pane is always referred to (and indicated in the toolbar) as an "Assistant" editor even if you didn't invoke the assistant (which is bafflingly denoted by a Batman icon button).
View options are under View, where they belong, instead of being incorrectly placed under the Window menu.
If you're typing a call to a function and you're using another function call as a parameter, Xcode's auto-completion appears to automatically prefer functions whose return type matches the parameter you're filling out. EXCELLENT.
But there are bugs aplenty. So many that it's very hard to get work done at times.
One particularly infuriating bug is Xcode's failure to indicate when and where it has stopped at a breakpoint. In many instances, it will stop and pull up the source file, but there's no execution point highlighted. The editor just shows the top of the file, and nothing happens as you step through. The current line is not highlighted, and nowhere does Xcode say, "Stopped at breakpoint." It just says "running."
There's no way to sort files your files in the treeview. NONE. Xcode 3 was bad enough in not sorting them automatically, making you go and sort them over and over and over through the life of a project. Now that's not even an option. WTF?
Xcode leaves your editor window littered with error highlights and messages even after you've fixed the code and recompiled. It turns out that these errors apply to a different target, even though you never built that target and the code they're complaining about doesn't exist anymore.
Xcode will overwrite your syntax-highlighting choices for specific symbol types. You can change them again and again, and Xcode will overwrite your settings inexplicably. You can watch it happen.
THERE'S NO "BUILD" BUTTON IN THE TOOLBAR, AND YOU CAN'T ADD ONE. In fact, the toolbar is not customizable at all, and there's only a "Run" button. What if you don't want to run? Yep, you have to look up the hotkey.
What did they do with all the extra space in the toolbar? Made the project-config dropdown NARROWER. It's so small that it can't show you WTF you're working on. Meanwhile, there's a vast strip of empty space right next to it. Unbelievable.
The Xcode team tried to clean up the mess that was project settings, adding the concept of "schemes." It's mostly an improvement, but buggy. But I'm out of time for this update...
I am not sure what kind of documentation they give you with Xcode 4, however there should be something in the help menu I imagine. WWDC also had a video on Xcode 4, it was their "State of Union" address. Here is a link to the iTunes videos.
Just to add to Luke's point, it all depends on how much code you know. I am going to stick with V3 as compile errors etc are not automatically fixed and I want to learn how the code works, this is going to help in the future.
Current tutorials (mostly about V3) will help you grasp the basics of Xcode, as V4 is easier overall but understanding the basics is the most important aspect.
Localization seems to be pretty significantly broken in 4.0, with constant crashes for me.
I would wait for 4.0.2, or something..
I just switched back to 3.2.6 after I tried out XCode 4. It has so many bugs and crashes, it was too frustrating. Also its updates are not included in the normal apple updates, you have to re install the whole software via the installer. Its ridiculous! Although the git integration and drop down syntax completion is cool, I think I will wait till 4.0.3 before updating again!
I am completely new to the whole FlashDevelop/Flash/etc toolchain, but wanted to do some experimenting. I installed FlashDevelop and Flex SDK on my laptop, and thinks worked out just fine, except for one thing: the compiler messages are localized!
Messages like "gebruik van een niet-gedefinieerde eigenschap" (Dutch.. sort of) are limiting my productivity. I don't recognize them because they look nothing like what I'm used to in any other programming environment, as a proper sentence they make even less sense than English error messages, and I certainly can't google them properly.
Now I've already seen there are a couple of xml files and java/mxmlc/fcsh/etc configs I can tweak, but nothing so far helped.
Please help me restore sanity and en_US/1033/etc! Thanks...
Edit Setting my windows locale to English through the control panel, then restarting FlashDevelop, did result in English error messages from Flex. So hurray, I've got a usable workaround. I'd still like the two to be unrelated though, as a developer a fiddle with those settings all the time.
Modify jvm.config file located in the same folder as your mxmlc.exe
by adding on java.args line the following option:
-Duser.language=en -Duser.region=US
Detailed explanation is here.
Goto Tools | Program Settings (press F10) and select Flash Develop from the left panel. Scroll down to the Misc heading - the last option is Selected Locale. If en_US is not there, then you have a problem - you might have to download the correct locale version again.
Setting my windows locale to English through the control panel, then restarting FlashDevelop, did result in English error messages from Flex.
I someone comes up with a better solution, I'll gladly accept that answer in stead of this one...