I have a form with multiple tabs, it has a receipt in the first tab in a rectangle box. Is there a way to just print that rectangle box using VBA?
Related
I made a notebook for saving latex into PNGs that I can later import into PDFs.
screen shot
I have buttons that add text to the textarea via .on_click(). Is it possible to set the focus back to the text area in the callback function?
I am trying to implement a series of layered widgets in Qt but having trouble with clicking "through" a top-level widget to one that is below
I have a standard main window that has a centralwidget, within this centralwidget I have a "button overlay" widget which contains a series of buttons around the side of the screen. The central widget then also contains a "display" widget within which I have a number of other widgets (In effect a way to display a center view with a series of buttons around the side)
However, I can only click on the buttons within the overlay, any buttons within the view don't receive the mouse click. I am assuming this is because although you can see the buttons in the layer below, it's the widget at the top layer that receives the mouse clicks which seems to be true as if I raise() the view to the top, the buttons can receive clicks
So, I there a way to click buttons through another widget or is my entire approach wrong?
How can i get the values of dynamically created text boxes that i have reload every time a user adds a new text box?
Right now what I have is a form with a few text boxes, and an add button, now when the a user clicks add button, it creates another section with a few more text boxes, but now if the user had typed something in one of the text boxes before he clicked add, how can i store that information and make sure it comes back up when the page reloads?
Thank you,
I'm new. I've determined I cannot make a label "active" and accept keyboard input, so I am trying text fields instead. Seeking advice as to how to kill off the built in keyboard when the user taps the text field, as I want to use my own keyboard (a series of images).
I can determine the active text field (textfield.editing == yes), but when I will kill of the keyboard it seems it also kills off the ability to enter any data into that text field.
Maybe I need to just "hide" the keyboard? Send it off the screen?
OK, I found a way to make this happen. I created some transparent buttons, and laid those over the top of the labels. When the button gets clicked, it designates the label below it should be the active label.
In a separate method, the users text runs thru a few conditions to determine which label (as designated by the transparent button) is active, and the text goes into that label.
I have a custom TextInput that listens for the FocusEvent.FOCUS_IN and FocusEvent.FOCUS_OUT events:
textDisplay.addEventListener(FocusEvent.FOCUS_IN, onFocusInHandler);
textDisplay.addEventListener(FocusEvent.FOCUS_OUT, onFocusOutHandler);
My onFocusInHandler function basically removes a "promptview" that tells the user to type in a value, with the onFocusOutHandler doing the opposite.
For example, if the TextInput text was backspaced to a blank value and the user clicks out of the TextInput box, it would show a "Please enter a value" light-gray prompt in the TextInput.
This works fine until the user clicks our custom "Clear" button. The clear button sets the text to "", and I can tell the FocusEvent.FOCUS_OUT is received because the prompt text is set to visible (its not being set anywhere else). The problem is, the cursor remains in the box as if it still has focus, so if the user immediately starts typing, both the prompt text "Please enter a value" and the user-entered text appears over the gray text, which looks pretty ugly and unreadable.
Why does the TextInput receive the FocusEvent.FOCUS_OUT event if it's not actually losing focus? Is there any way I can get around this?
Option 1. Use the Spak TextInput in Flex 4.1 or 4.5. This already provides a promptDisplay by default (as mentioned in the comments)
Option 2. Take a look at the focus-skin. This skin class is usually placed on top of the normal skin. There could exist some focus ambiguity between these two. Try using a custom focus-skin without a textDisplay and clear button.
Option 3. Not only use a focus event to show or hide the prompt, but also look at the content of the TextInput. You don't want to display a prompt when the text is set by binding as wel.