I have a Java GUI that I'm developing and I've run into a snag with regard to the default size of the "thumb" on a JSlider I need for user input for the simple and unavoidable reason that the application has to run on a touch-screen, there is no mouse, and the precision of the touch of a finger is just not good enough to make it easy to "get a grip" on the slider to move it. The touch screen is all there is... it just isn't that precise.
NO PROBLEM, I thought! I'll just customize it and make the "thumb" bigger! In doing my research I found this previously asked question, and it has what looks like helpful data, but I couldn't figure out how to get that to work. In the answers to that question it points to this page where it purports to show how it's done, but ... it then doesn't show it?!
I guess they presume you know what to do with the likes of:
Slider.thumbHeight Integer
Slider.thumbWidth Integer
But, I don't! Anybody got any code snippet of an example?
I played around, incompetently, with stuff like this that I really don't quite understand:
UIDefaults defaults = UIManager.getDefaults();
defaults.put("Slider.thumbHeight", 45);
defaults.put("Slider.thumbWidth", 15);
...With no success, though it does compile just fine. I tried creating the slider after this. Nope. I tried mySlider.updateUI(); Nope. And, of course, this won't compile at all: mySlider.thumbHeight(40); ...I just don't quite grock how one is supposed to customize these things.
Thanks in advance.
Old post I know, but still may be relevant for others anyway.
"Slider.thumbHeight Integer" just tells you that the variable is of type integer and thus expects a whole number as an argument when you set it.
You have to change the UIdefaults (as in your example) before you create the JSlider.
This said it seems to be operating system dependent whether it works or not. It worked well on my Windows10 PC but not on Raspbian Linux where I really needed it :-(
Related
First time here, I hope I'm doing it right and I hope I'm allowed to ask this here.
I'm making buffer layers out of points in QGIS 3.8.1 Zanzibar, it's 5 point layers and I need to generate the 5 corresponding buffers. They come out alright, but after I load a previously saved style for the layers the geometries simply disappear.
I have:
Ticked layer off and on, still gone.
Deactivated any other layer and make sure it's not hidden behind something else.
Zoomed to layer, not the problem, it zooms where they should be, they're just not visible
Checked for SRC, it's all good, all of them are the same.
Open attribute table, all the data is there and it's correct.
Left click on layer/layer visibility and made sure it is unchecked as it should, I also tried checking it to no avail.
Made the layers all over again, same result.
Went to Properties/Source/Query Builder and wrote this (I saw this in a vid where it worked):
"FIELD" LIKE "FIELD"
Where "FIELD" is a field of my attribute table, tested it correctly and applied...didn't work either.
Just one seemed to come out alright before doing all this, but I followed the exact same procedure for all of them.
Any ideas? Do I have to re-do the style all over again manually for every layer?
Thanks in advance!
I just found out what was wrong, I hope this helps someone in the future:
The style I saved was classifying data based on a particular column, wich of course, must exist and have the exact same name in the other layers in order to work. I just forgot to generate said column on the rest of the layers.
Cheers and thanks to the editor.
this is my very first entry here, may it not be the last....
I am having a bit of a struggle with some GUI stuff.
I really have an animation up front my eyes and it should look like the following: using c# with desktop application.
This Form looks like a login window with server address, username and pw textboxes and with a connect button as well, so nothing special. Size wise it can be small or at least same as size as the turned window. doesnt matter at the end.
once you entered your credentials and all turns out to be fine, connection is there and valid.
The main Form is suppost to flip then (doesnt matter horizontal or vertical),
and shows you your options you got then in this newly window. kind of an animated sign, that you are logged in and have now these options.
But the flip is suppost to stay on the same place. Like a card flip or a coin flip, but just the whole form and it ends then at the same place as before.
(sounds really wired to explain)
This can also be done with a new form poping up, just with a animated turn over, no problem with that.
And this is exactly where I am stuck.
I really cant find any information on how this would look like in code or even in animation.
I am using c# and the basic project started as a desktop application project, which it will be at the end.
Its been a while since my last coding, please be gentle.
i know there are plenty of entries in here also in google as well, but i didnt found anything which will do this for the main window as a total. images etc: yes, but for the whole form: no.
Any help out there?
May be tehr eis a trick i am not aware of? Its been a while since the last coding work, I need to admit that.#greyhairsarecomming
many thanks in advance! much appreciated
kind regards TG
I have been looking for a way to pull something out of my main method into a outer method then plop the output of the outer method back into the main method (this is in Eclipse).
I have been looking for a strangely long time for a answer for this but everything seems way more advanced than what I am looking for. If anyone can help it would be a great help.
You want the extract method refactoring. Select the code block that you want move into a different method and press Shift-Ctrl-M. Or is it Ctrl-Alt-M? Can't remember right now.
And here I go giving refactorings to someone that doesn't even know what a method is....
I have a database that I work on using Access 2013, though I must maintain compatibility with Access 2010; I am using Windows 7.
I have an input form that is set to Pop Up = Yes, and Modal = No. When opening this input form directly from the Navigation Pane, it functions perfectly normally.
I have a macro in a search form that calls up this input form with the specified record using the "OpenForm" action. When opening the input form with this macro, the form's background is totally garbled (it pulls the background image from whatever was behind it when called, as though it were transparent), and all labels are unreadable.
That said, if I run the macro again by trying to open a different record, the form then appears correctly until it is closed. Also, if I change the "Window Mode" in the "OpenForm" action to "Dialog" rather than "Normal," it appears correctly.
Neither of these are valid solutions, though -- it should work on the first time, and I do not want the form to be modal. All my code seems okay (insomuch as I am not receiving error messages), so I don't understand why it would be doing this... any guidance is very much appreciated.
I have discovered what is causing this problem, though I don't understand why.
The macro I am using came from a sample database, and has some commands I am not fully familiar with. One such command is "Requery."
I experimented with removing various parts of the macro with the window mode as "Normal" for the "OpenForm" command. As soon as I tried removing "Requery" (and nothing else) the window opened in "Normal" mode with no distortion whatsoever.
In short, having "Requery" in the macro was what was causing this error to occur. It seems like an innocuous enough action (all it does is refresh data, from what I understand, as described here: https://msdn.microsoft.com/en-us/library/bb177360(v=office.12).aspx), but since I don't see why its inclusion was necessary anyway (if anyone could shed some light on that, it would be appreciated), it looks like this is essentially solved.
I hope this may help someone else in the future!
I've seen that this question has been asked a few times, but no one seems to have an answer. I am trying to create an autocorrect feature on a custom keyboard, but I am completely lost as to how to do so. Apple gives some documentation, but it's not very detailed. I know it has something to do with UILexicon data, but I'm not sure what to do with it and how to use it to correct strings of text the user is typing.
Any help would be greatly appreciated.
What I have found so far:
let controller = UIInputViewController()
controller.requestSupplementaryLexiconWithCompletion({
lexicon in
println(lexicon.description)
})
But this is as far as I've gotten. Not sure what to do from here.
You are asking a very difficult question. In short, there is no built in access to autocorrect on iOS8; there is also no access to the APIs on iOS that allow the system to do things like show the red 'possible error' underline effect, or to other aspects of the system autocorrect behaviour, such as the in-place suggestion dialog (on iOS 7, or if you do not have the suggestions bar visible) or the 'will correct' blue background (on iOS 8).
things you can't do:
in-place error indicator
in-place autocorrect dialog
suggestions bar autocorrect indicator
what you can do is write your own autocorrect engine, from scratch, including both your own text processing and analysis and your own user-interface idioms. This has to all be done with the limitation that you are not able to draw outside of your keyboard's bounds, and you cannot modify anything else on screen. A number of third-party keyboards do this, such as minuum and swiftkey (disclaimer: I work on minuum) but it is a non-incidental amount of work. If you're interested in playing around with this, a good place to start might be the built in UITextChecker class, although auto-correction is ultimately a problem distinct from spell-checking.
UILexicon is only useful once you've already implemented things; all that it really offers you is a list of words that you can use to supplement whatever dictionary you're using, as well as to implement any text shortcuts your user might have added in their system settings. It is not, on its own, enough to build an auto-correction system from.
addendum:
How to Write a Spelling Corrector is a great little essay / tutorial by Peter Norvig that you might find interesting, and that I would recommend even if you're not trying to write auto-correct.