The duration for geany is too short, how can I increase the duration that the calltip stays on? Or have geany show the required parameters for a function that stays while I type them in?
You can show the call tip indefinitely through a key-binding which can be edited in settings.
Related
I really like the Tips in IntelliJ IDEA to learn more about its helping functions. But I tend to start the IDE multiple times a day and get a new message every time. Then the same messages are getting annoying and I usually wont even read them anymore.
So I would like to set the tip of the day to daily as the name suggests.
I didnt find a setting in the program or on their help pages.
Is there a config file or some other possibility to do so?
There is no such option. What you can do is disable this window.
To do this, click on Help > Tip of the day and uncheck Show tips on startup.
Whenever you want to see a new tip navigate to this same place and read as many as you wish.
But no, there is no option to display it only once a day. It shows up whenever the IDE is started.
Today, when I try to use the location simulation, I find it is unresponsive.
Prior to this, I was able to resize the simulator, and go to any location. Today, none of these inputs work.
Also, is it possible to change the default lat/long in the simulator?
It currently defaults to a location that is not very useful to me.
Thanks,
-Craig Lang
Horizon Technologies
You can change the default location by entering your desired Latitude and Longitude to the fields provided and Update, then close the location window.
Whenever you run app, it will now default to that location. I agree that location simulation should remember your last used location when it's opened and it shouldn't change the default to New York. I believe this is something Codenameone team could provide.
Your location simulation maybe freezing if you're using the update Piotr provided, as it may contain minor bug. Check if you are getting any Exception in your console.
Maybe these pull request are solutions:
https://github.com/codenameone/CodenameOne/pull/1703
https:/github.com/codenameone/CodenameOne/pull/1707
The first one added all locations parameters to the form and remove update button as not needed, you need just change value or move you mouse wheel. This pull request was accepted free days ago so it should be on production?
The second one add store form fields and waiting for accept.
New Location Form
I started a putty window, changed the font, and then did Windows-Left to fit it to the left side of the screen and it decided to do the screenshot below. The only way i've found to make it go away is the log off/on but that's obviously impractical and doesn't fix the problem.
I've had it in the past but not this bad. It usually happens when I move or resize the window. Is there a setting to have it just auto resize by default?
[edit] and then, about :05 later out of nowhere, it popped away. I'm just sitting here doing something else and it changed back to normal.
That means that you (or someone else) is connected to the same Byobu session from another computer with a smaller terminal size.
You should be able to kick the other session using Alt-F6.
Full disclosure: I am the author and maintainer of Byobu.
For mac user, by querying from the help info ctrl-a + ?, one could simply run the bash script $BYOBU_PREFIX/lib/byobu/include/tmux-detach-all-but-current-client to kick other sessions.
I have created a user control that has an image that I would like to "blink" at the same rate as the user caret. This can be set using keyboard settings in the control panel on windows systems.
Are there any classes that will help me obtain this value?
I always thought the default was .5 seconds, however this is faster than desired and can be modified.
Regards
Answered my own question, answer for people looking in the future.
SystemInformation.CaretBlinkTime
I have a webpage where I am waiting for a button to appear, and when it appears I would like to click it. The button is on a timer and may take as long as an hour to appear. Also, if the button takes longer than a certain length of time to appear, I'd like to move the mouse (otherwise the website will log me out automatically).
So, to wait for a button to appear I devised this Sikuli script:
button = "button.png"
while(1):
if exists(button):
print("found it")
click(button)
break
else:
print("wait longer")
wait(button,30*60)
# do a regular task
print "all done!"
The above does not seem to be functional. If the button is on screen, the script will find it... However, if it has to wait it will simply time out quickly with a FindFailed exception (on the click() even though the button does not exist on screen). I considered writing a handler, but seems like overkill.
What am I doing wrong and what is the best way to wait a long period for a visual event like this?
Some other thoughts for you...
while(1):
wait(Button, 30*60) # This will spinlock for 30 minutes for the button to appear
if exists(Button):
hover(Button) # Debug statement allowing user to see what Sikuli has matched to
click (Button)
else:
mouseMove(Location(50,100))
mouseMove(Location(50,200))
Links:
wait
mouse movement link
Location
Maybe Sikuli recognizes something that looks quite your button, and tries to click it.
If you right click in the IDE your button pattern, you can fine tune the tolerance level for recognition. Try to cut the image exactly around your button and increase the value to be more precise.
I suggest you to read this tutorial
http://doc.sikuli.org/tutorials/surveillance/surveillance.html
and to set up a event handler to manage your button when it appears
http://doc.sikuli.org/region.html#Region.onAppear
http://doc.sikuli.org/region.html#observingvisualeventsinaregion
It is not much code to write.
You can get a nice example with full source code in Sikuli's Blog here
http://sikuli.org/blog/2011/08/15/sikuli-plays-angry-birds-on-google-games/
I think you can just set up your handlers and go with
observe(FOREVER)
If you want sikuli to do stuff while your waiting for an image i would use the onAppear(pic, function) and observe(FOREVER, true) methods this is how it works
event = Sikuli.event
def function(event):
click(yourButton.png)
onAppear(picYourWaitingFor.png, function)
observe(FOREVER, true)
basically what this does is onAppear will continuously scan the screen for picYourWaitingFor.png. sikuli continues execution after words so it's scanning while its working. on the appearance of said pic it will jump to the function you put down as the second parameter of onAppear.
I have this same issue as described. Its not about waiting forever. And Observe won't work either, because that does watch forever. Think about wanting to check for event only for a certain period of time say 60 seconds. If it doesn't occur, move on. This could be happening in a specific series of events. If the image doesn't appear in the 60 seconds, move on to do another series.
wait(image,60)
...will crash after 60 seconds if it doesn't find the image, which isn't what is wanted at all in my case.
So I did something like this:
attempt = 1
count=0
while attempt:
if exists(image):
attempt=0
else:
count=count+1
if count>60:
attempt=0
else:
wait(1)
Probably a better way and doesn't give an exact time, but approach doesn't crash the script.
You could also try: except it.. Should be shorter.