Buttons – Synonym for action of completing a form

I can't believe I'm essentially begging Stack Exchange to find a synonym, but I'm stumped. I have tried all the thesaurus and thesaurus.

So the Customer Service Representative (CSR) has created one or more accounts by type for their customer, and now they have a small chart of accounts, but the accounts are still empty. The CSR must now open each to complete it.

I am looking for one or two short words for a button in each row that the CSR takes to an account to enter all the data, that is: (Click here to complete all the details of this account):

enter the image description here

(EDIT) is the most obvious button, but frankly, editing generally implies that there is something there to edit. This is the first time.

(Complete) (Complete) is awkward.

* Warning: for some reason, we don't use the word "form" for these … forms. We each call a "request" (since you are "requesting an account").

(Complete) You can fill out an application, but for me that implies that it is mostly done and you are just completing it. And Complete is also a noun; it could be very ambiguous to see a button with the word & # 39; Complete & # 39; at.

(Start) (Open) (Go to)?

(I have tried many others, which I have not listed here)

19.10 – How to configure buttons on the Wacom Bamboo CTH-470 tablet to click with the mouse

I have a Wacom Bamboo CTH-470 running on Ubuntu 19.10, everything works perfectly, from stylus to pad, however the tablet buttons are not recognized, well they are recognized but have no other action other than on the setup menu. I went through a lot of searches, links and guides to finally recognize the buttons "correctly", which means I went from xinput to xsetwacom to finally understand how to assign the buttons to their proper physical position. The only way I have to verify this is through "wacom settings / devices / tablet" and when I click on the "Tablet" tab and click on "Map buttons …" I can see the four buttons for the which gives me four options to select: "Defined application", "Show online help", "Change monitor" and "Assign keystroke".

When I press each of the buttons it shows the proper button selected and gives me these options. However, I want to use the buttons as mouse clicks, as right click, left click etc. I thought it would be obvious, but apparently it is not, I ran:

~$ xinput

⎡ Virtual core pointer id=2 (master pointer (3))
⎜ ↳ Virtual core XTEST pointer id=4 (slave pointer (2))
⎜ ↳ ETPS/2 Elantech Touchpad id=16 (slave pointer (2))
⎜ ↳ Kensington Expert Wireless TB Mouse id=13 (slave pointer (2))
⎜ ↳ Wacom Bamboo 16FG 4x5 Pen stylus id=17 (slave pointer (2))
⎜ ↳ Wacom Bamboo 16FG 4x5 Pen eraser id=18 (slave pointer (2))
⎜ ↳ Wacom Bamboo 16FG 4x5 Pad pad id=19 (slave pointer (2))
⎜ ↳ Wacom Bamboo 16FG 4x5 Finger touch id=20 (slave pointer (2))
⎣ Virtual core keyboard id=3 (master keyboard (2))
↳ Virtual core XTEST keyboard id=5 (slave keyboard (3))
↳ Power Button id=6 (slave keyboard (3))
↳ Video Bus id=7 (slave keyboard (3))
↳ Sleep Button id=8 (slave keyboard (3))
↳ USB2.0 UVC 2M WebCam: USB2.0 UV id=9 (slave keyboard (3))
↳ Asus Laptop extra buttons id=14 (slave keyboard (3))
↳ AT Translated Set 2 keyboard id=15 (slave keyboard (3))
↳ Kensington Expert Wireless TB Consumer Control id=10 (slave keyboard (3))
↳ Apple Inc. Apple Keyboard id=11 (slave keyboard (3))
↳ Apple Inc. Apple Keyboard id=12 (slave keyboard (3))

From where I get the id: 19 for the tablet, then:

~$ xinput get-button-map 19

1 2 3 4 5 6 7 8 9

This tells me that the buttons are assigned, but when I click on them nothing happens. Then I wrote:

~$ xinput list 19

Wacom Bamboo 16FG 4x5 Pad pad id=19 (slave pointer (2))
Reporting 8 classes:
Class originated from: 19. Type: XIButtonClass
Buttons supported: 9
Button labels: None None None None None None None None None
Button state:
Class originated from: 19. Type: XIKeyClass
Keycodes supported: 248
Class originated from: 19. Type: XIValuatorClass
Detail for Valuator 0:
Label: Abs X
Range: 0.000000 - 0.000000
Resolution: 0 units/m
Mode: absolute
Current value: 0.000000
Class originated from: 19. Type: XIValuatorClass
Detail for Valuator 1:
Label: Abs Y
Range: 0.000000 - 0.000000
Resolution: 0 units/m
Mode: absolute
Current value: 0.000000
Class originated from: 19. Type: XIValuatorClass
Detail for Valuator 2:
Label: None
Range: 0.000000 - 1.000000
Resolution: 1 units/m
Mode: absolute
Current value: 0.000000
Class originated from: 19. Type: XIValuatorClass
Detail for Valuator 3:
Label: None
Range: 0.000000 - 1.000000
Resolution: 1 units/m
Mode: absolute
Current value: 0.000000
Class originated from: 19. Type: XIValuatorClass
Detail for Valuator 4:
Label: None
Range: 0.000000 - 1.000000
Resolution: 1 units/m
Mode: absolute
Current value: 0.000000
Class originated from: 19. Type: XIValuatorClass
Detail for Valuator 5:
Label: None
Range: 0.000000 - 1.000000
Resolution: 1 units/m
Mode: absolute
Current value: 0.000000

From this I guess the problem is that the "button labels" are missing and that is the reason why they don't take any action.
My question is: am I correct in assuming this? If so, how can I modify the "button labels"? And if I'm wrong, what can I do to assign left, right and middle clicks?

If anyone can help out here it will be greatly appreciated.
Thank you!

javascript – Plain text slide show and buttons

Oops good afternoon i have a problem i need to make a slide show on a website however i need the text of the image to change according to the image displayed on the slide, and something else i should do is that the color of the buttons to change the image change the color of the button according to the slide
Javascript 🙁

var imgs=();

slider var;
var img_atual;
var max_img;
var tmp;
var change_time;
var vtempo

pre_loading () function {
var s = 1;
for (var i = 0; i <3; i ++) {
imgs (i) = new image ();
imgs (i) .src = "https://pt.stackoverflow.com/imgs/s" + s + ".jpg";
s ++;

load_img (img) function {
slider.style.backgroundImage = "url (& # 39;" + imgs (img) .src + "& # 39;)";

function starts () {
pre_loading ();
img_atual = 0;
max_img = imgs.length-1;
slider = document.getElementById ("main")
load_img (current_img);
change_time = 0;
anima ();

swap function (dir) {
change_time = 0;
img_atual + = dir;
if (img_atual> max_img) {
img_atual = 0;
} else if (img_atual<0){ img_atual=max_img; } carregar_img(img_atual); } function anima(){ tempo_troca++; if(tempo_troca >= 500) {
change_time = 0;
exchange (1);
window.requestAnimationFrame (anima);

function image1 () {
load_img (2);
document.getElementsByClassName ("bt_local"). style.backgroundColor = "blue";
function image2 () {
load_img (1);
document.getElementsByClassName ("bt_local"). style.backgroundColor = "blue";
function image3 () {
load_img (0);

seedling function () {
document.getElementById ("bt_local"). style.backgroundColor = "blue";

window.addEventListener ("load", start);



#main{width: 100%;height: 300px; overflow: hidden;display: flex;

justify-content: space-between; align-items: center;}
.imageBg {
top margin: 1px;
width: 1400 px;
height: 450 px;
Bottom Size: Cover;

.bt_slider {
Transparent background;
font size: 26px;
height: 30%;
width: 30px;
color: #FFF;
cursor: pointer;
scheme: none;
margin: 10px;
edge: none;
edge radius: 2px;
.bt_slider: hover {
Transparent background;
.bt_local {
edge radius: 50%;
background color: gray;
edge: solid gray;
top margin: 20 px;
left margin: 2px;
height: 10px;
width: 10px;
cursor: pointer;
.bt_local: hover {
background color: black;
border color: black;
.botoes_imagem {
user selection: none;
left margin: 48%;
.text_fotos {
align text: center;
White color;
font size: 16px;
top margin: -500px;

javascript – Create nextPage and prevPage buttons with ReactJS hooks

I'm having trouble creating the nextPage and prevPage buttons with useState. Obs (in the backend I used lib mongoose-paginate, in the request it gives me the options of page, limit, pages and etc.)

import React, {useState, useEffect} of & # 39; react & # 39 ;;
import api from & # 39; ../../ services / api & # 39 ;;

import & # 39; ./ style.css & # 39 ;;

Main () function {

const ( user, setUser ) = useState(());

const ( page, setPage ) = useState(1);
//const ( totalPage, setTotalPage ) = useState(0);
const ( limitPage, setLimitPage ) = useState(3);

useEffect(() => {
    api.get(`product`).then(response =>{

        const { page, limit } = response.data;


}, ());

async function nextPage(){
    if(page === limitPage ){
        const f = await api.get(`product?page=${page}`);


{user.map(use =>(

{ use.title }

Descrição: { use.description }



export default Main;

You need to have 2 fixed buttons – Register and chat

I have a customer requirement to have 2 fixed buttons on the home page. One is for registration and the other is for Chatbot. I need suggestions on which location would be best with the least impact on chatbot discovery and registry conversion.

Solutions I have in mind:

  1. Have a sticker registration button in the left corner and chat
    button in the right corner.

  2. Have the record button in the navigation bar and the chat button on the right

  3. Combine the button for registration and chat in a single sticky unit.

  4. Move the record into the page layout and have it as a banner on
    between article sections (like an ad section; we don't have ads on
    the website)

Which one would you vote for? or better solutions?

Calendar zoom buttons: should they zoom from the current position or from the current date?

I have a calendar and there are 3 buttons to zoom and show a week, month or year. When you click on any of them, should the zoom center be the current date or the center of the graphics window?

Am I wrong and in fact it is not strange that some elements of a group of radio buttons do not generate events?

In a discussion under this answer to Make PySimpleGUI radio buttons generate events I expressed that I felt that if some buttons (items) in a single group of radio buttons generated an event and others in the same group would not, it would be "strange".

I think it is strange to have a group of radio buttons where some generate events and others do not. My only examples before this were the actual buttons on the radios where the term originates from, the Matplotlib RadioButton widget and every user interface I have used as an end user. Then it is de facto Weird for me.I'll look at some other examples now to see how common the mixed buttons are (some triggering events, others not).

I'm wrong?

A simple way to answer could be to simply give one or a few examples where this would be used and a package in addition to PySimpleGUI provides it.

magento2.3: all buttons in a store redirect to the page not found

I am using a multiple store.

The first store works perfectly but the second one has a problem.

when we click a button (add to cart, create account, contact)
redirect to page & # 39; error 404 & # 39; Not found.)

It is not the first time that I create a multiple store, but I never had this error.

I specify that I am using magento 2.3.2 (it was 1.9 before migration), php 7

Please help

unit: problem with instantiating buttons and variables in Unity3D

I'm currently trying to make a system where a button inventory is created and at runtime the buttons are placed in a GUI component (Panel). I used a button list that is created at startup and creates X number of buttons for X number of spells found for that player, and for some reason the created button doesn't recognize any changes made to it:

    public void createButton(int index)
        var panel = GameObject.Find("ButtonPanel");
        Spell spell = GlobalControl.Instance.spells(index);
        GameObject button1 = (GameObject)Instantiate(ButtonPrefab);
        button1.GetComponent().text = spell.spellname;
        //get prev button position
        float yindex = 130.0f - spellinv.Count * 35.0f;
        button1.GetComponent().SetInsetAndSizeFromParentEdge(RectTransform.Edge.Left, yindex + 0, 10);
        button1.layer = 5;

There are no runtime issues, however RectTransform does not alter the position it is in (0,0,0), and the text is still set to the prefabricated default "Button", it seems to register nothing that applies to the button, except for the layer settings.