I have a gui that has a label which I would like to have text change based on the section of the test that is being performed. However, it doesn't change immediately but waits for the user input (i.e. messageBox). But I want it to automatically update. Is there anyway this can happen?
I tried using configure which changes the text but it doesn't happen as soon as the line of code is encountered. Do I need to focus on the label first and then unfocus? If so, how do I use the focus command?
Add update idletasks after you have configured the new text.
Related
I try to use SikuliX IDE to fill more than one input fields on the same screen. All the fields look like the same. I captured input field, click on it and use type to set value, but text is not present after that process.
Try wait() function between your actions, sometimes you need to wait the gui to get ready for your next action. The default time gap between actions may too tight.
So I am creating a database and need to enter two titles into a text box. I want to type the first one, and when I am done I try to hit "enter" to jump down to the next line but all it does is save what I entered and exit the text box. What I am doing wrong? I'm so used to just hitting "enter" when I'm in Microsoft Word to start a new line but that does not seem to be how it works in Access.
Press control-enter to get a newline.
Just a tip: If you are entering two values in a single field like that, you have a badly designed table structure.
Is this text box in a table/query grid view or is it a control on a form? If it's on a form, then in design mode there is a property of the text box called Enter key behaviour that you can use to determine whether focus should jump to the next control or a new line should be entered within the text box (as you're after).
I've a text view and a method has a while loop does things among them appending to text view
But The text only changes when the method ends.. (but the console shows changes instantly
How to update it instantly??
You have to give the UI, i.e., the gtk code, the chance to update the pixels on the screen. The update happens when your method exits because that is when gtk gets back in charge and can do the changes. If you want to do a lot of work and still update the UI just execute the work in a separate thread and update the UI by calling Gtk.Application.Invoke() from time to time.
I think I'm looking directly at an Access 2003 bug. Here's what I did (I think):
I'm developing a Continuous Form (i.e. multiple records per page).
I have an unbound textbox in the background of the Details section. Under Data Properties, I have Enabled=No and Locked=Yes. (In other words, I don't want the user to select it. I only want it for the background color)
This textbox also has some conditional formatting to change the background color for that row. (e.g. If we haven't spoken to that customer in awhile, the background for that record is red)
If I choose a record where the conditional formatting is active (i.e. the background is red), I can actually click on this textbox. There's not much that I can do, of course, but this shouldn't happen and surely would be confusing to the end-users.
Has anyone else seen this? What's your workaround?
Enabled is a property that can be controlled via conditional formatting. By default when you add a new condition, the Enabled property is set to True. If you don't want your control to be enabled you must explicitly set Enabled = False within the conditional formatting rule.
The property is toggled via a button in the lower right corner of the conditional formatting dialog. It's easy to miss (I forget about it all the time).
Personally, I think the property should be three-way: True, False, or Inherit (with Inherit as the default). Unfortunately, Access forces you to be explicit when adding conditional formatting rules and state whether the rule should make the control Enabled or Disabled.
Here's my workaround (I was waiting to see if anyone else would suggest something better. Apparently not.)
In my conditionally formatted textbox, add an Event Procedure for GotFocus. Enter this code: Me.Txt_FocusHere.SetFocus.
Make a 2nd unbound text box somewhere on the form. Shrink it until it's just 1 line thick. Call it Txt_FocusHere.
So whenever the user clicks on the colored background, the focus is immediately taken to this dummy textbox which can't store any data and is so small that the user doesn't see the blinking cursor.
I successfully used the method on the following page: http://www.mvps.org/access/forms/frm0047.htm - "Changing the Background Color of the Current Record in a Continuous Form"
I have a form that is used for data entry, and on one form there is a text box that is used to enter notes. However, if the user hits <ENTER> I need the cursor to stay in that text box and start a new line, but currently it is jumping to the next control (text box).
Is there a simple property setting that would do the trick? Or a VBA method that would accomplish this?
In Ac2003, there is the "Enter Key Behaviour" property, which gets set to "New Line in Field".
I suspect Scott's answer is what you're looking for. That property is available in Access 2007 also.
Another option would be to have the users enter CTRL+Enter to insert a line into the text control. Your users may not go for it, though.