linux – How to set unchangeable entry in bash dialog checklist?

I found out how to use the --checklist option on bash’s dialog command. However I want to set some entries on the checklist to show up, but not be toggleable, so they are permanently on. Does anyone know how I can do this? You can turn check boxes on and off, but

android studio – WhatsApp clone dialog popup view


Your privacy


By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.




What is the meaning of “[*.]” in the Chrome cookie exceptions dialog?

enter image description here
Screenshot of the add-to-cookie-whitelist pop up (chrome://settings/cookies?search=cookies)

I am always entering the metacharacters (*.) here, what is their meaning? Do i correctly guess that () means zero or one, * means one or more letters from “a” to “z”, and . means the literal “.”?

(some 300+ points owner: would you be so kind to append metacharacter to the tags of this question and then delete this paragraph?)

Is there any way to open the default Share item dialog from the SPFx webpart

Is there any way to Open the Default Share Item dialog from the SPFx web part’s details list (Modern dialog)?

enter image description here

My requirement is to open the default OOTB share item dialog (as displayed above) when someone clicks on the context item inside the Details list item.

8 – Dialog form submit button fails to trigger submitForm()

I load this form into a dialog using:

$content = Drupal::formBuilder()->getForm('Drupalweb_coreFormMyForm');
$response = new AjaxResponse();
$response->addCommand(new OpenDialogCommand($title,$content));

And the form is properly rendered inside the dialog. Problem is that when I click the submit button my submitForm() isn’t called. None of the tasks inside the function are performed. Even a dpm() shows nothing. And the redirect after submit doesn’t work either.

Here’s The actual form

class MyForm extends FormBase {
... 
public function buildForm(...) {
...
$form('action')('submit') = (
  '#type => 'submit',
  '#value => t('Select'),
);

public function submitForm(array &$form, FormStateInterface $form_state) {
  dpm('Inside form);
  Drupal::entityTypeManager()->getStorage('my_app')->load(1)->delete();

$form_state->setRedirectUrl($url);
} 
}
}

None of the things inside the submitForm() runs. This form submits normally when outside a dialog. Pls What could be wrong here?

penetration test – How to send dialog box to a device

I want to send a dialog box to a device with a preferred metasploit, and when the person clicks ok, I want them to install an apk, I created a backdoor in the original apk, but I don’t know how to display a dialog box. Does anyone have a guide to give me? I don’t know how to do this, but if someone gives me a guide I’ll learn

forms – Should closing the dialog clear its fields?

I identified as the most preferrable strategy for user not to lose their data implementation of confirmation/discard dialog when exiting original one.

enter image description here

enter image description here

I expect a few more form dialogs to emerge in the app though, for example editing of the profile.

enter image description here

Nielsen Norman Group’s research supports the use of confirmation dialogs, but they also point out not to overuse them, so they do not lose significance (see https://www.nngroup.com/articles/confirmation-dialog/). I feel the same, I don’t want to add Confirmation/Discard dialog everywhere. I believe if ‘post’ is going to be the most significant part of the application, it makes sense to put a confirmation/discard dialog there, but I feel less positive about putting it also on profile editing.

My question therefore is, assuming that we do not want to use confirmation/discard dialogs everywhere in the app, what’s the preferred strategy for the rest of the forms/dialogs?

This is what I can’t decide about:

  1. User can close dialog accidentally, open it again, but realizing that they lost their editing and data – getting annoyed.
  2. User can close the dialog as an act of discarding, but after a moment opening it again, expecting original data, but seeing the last uncommitted changes from the previous editing – getting confused.

What could be the ratio of these two scenarios occurring?

I noticed that most of the big web platforms do not preserve changes in their secondary (in terms of importance) dialogs. I wonder if it is based on a UX decision or if it makes just more sense in their scaled implementation.

For more context: Esc, Click on overlay/backdrop, and Close button (that I am yet to put everywhere) do close the dialogs.

applescript – Choose from list apple script service execution from Safari opens Firefox to display the dialog with list

Im trying to use following Apple Script to display a choose from list and perform certain actions based on the choice of selection:

set selectedOption to choose from list {"Open", "Edit", "Copy"} with prompt "Please make your selection:" without multiple selections allowed and empty selection allowed

But, whats happening is; when the Automator service runs, it opens Firefox to display the list of options. It would be a great help to understand this behavior, because Firefox not being the default browser it is waste of CPU resource to open it.

research – Are there any studies of users getting jaded of dialog requests?

Dialog boxes are needed. In the old HCI thinking, a user interface is essentially a dialog between a human, and a computer.

However, handling of the dialog boxes can become habitual. The typical example is Word or any similar document editor: when you close an unsaved document, usually, you don’t want to save it. In those exceptional times when you actually want to save it, you’re prone to click “don’t save” anyway.

Therefore, it is a recommended best practice to avoid opening dialog boxes often. Provide forgiveness instead of asking for confirmation: provide a way so that the user can undo. If you look at document editors on iOS (Pages, or OmniOutliner), they don’t have confirmation dialogs at all, and I guess the Lion version of Pages doesn’t have it either.

Also, the users are sometimes not able to comprehend the situation in question. Like, in this case, I bet an average user doesn’t really know, what “Microsoft Windows Component Publisher” means. There is no meaningful action in this case from the view of the user.

In other cases, the dialog box doesn’t tell the user what can he do, what would be the result of each of the choices, and how would the user benefit from those possible futures. Always provide the right context, and make the options always clear from the users’ perspective.

The users are always trying to achieve a goal. If the goal is to remove an application, they do whatever it takes to remove the application, even if a dialog box tells them it also removes their whole windows installation, publishes their nasty pictures on the internet, and sell their soul on eBay.

Together with this, and the habituality of choosing a default option, it’s rather discouraged to do dialog boxes most of the time.

I’ll grab the studies for you, and edit this answer in a moment, just couldn’t find it at Nielsen (useit.com – albeit I’m sure it’s there), but I have a few UX books lying around here.

Edit: Unfortunately, I didn’t find the usual psychologic journal stuff about this,as this has been a known fact since the eighties, and even writers from the nineties were too lazy to cite these studies correctly.

  • A case study from the Nielsen-Norman group is here
  • General guidelines for error pages from Nielsen is here, and there is a course where they tell you about Dialogue Design
  • Raskin was famously a big enemy of dialog boxes (look at the Canon Cat), and he describes these problems in The Humane Interface, Chapter 2-3: Locus of Attention
    • He also cites Baars, Bernard J. A Cognitive Theory of Consciousness (Cambridge, U.K: Cambridge University Press, 1988) and Card, Stuart K., Thomas P. Moran, and Allen Newell . The Psychology of Human-Computer Interaction (Hillsdale, NJ: Lawrence Erlbaum Associates, 1983), although I have no idea what these writings contain, and I have no access to them
  • Chapter Five of Norman’s classic Design of Everyday Things deals with errors, but it does deal with it in the physical environment, as the whole book tries to use the physical environment as a metaphor for the virtual one.
  • Jeff Johnson talks about interface issues in Designing with the Mind in Mind, for example in Chapter 6, _Pop-up message in error dialog box”, but he doesn’t tell about habits.

I could also quote the Apple Human Interface Guidelines (or iOS guidelines) and perhaps also the Windows Interface Guidelines, but they are about practical issues. Also I grabbed two other UX books and I could grab a 90s edition of SEPA (Software Engineering: A Practitioners’ Approach), where I remember there was the 10 commandment of user interfaces, that was an often-quoted UI rule-of-thumb guideline, but I don’t think I’d find its reference.

All in all, it seems this is something that we understood for 30 years, and everyone is just too lazy to back up their claim. Perhaps it is this way because everyone knows from their private life how easy is to make such mistakes, and it is the most easily tested thing in experimental settings.

As for what to do instead of error boxes, read Raskins’ book, or Norman’s book. As for looking at how an alert-less application flow looks like,look at Google Docs or Lion / iOS 5 versions of Pages.

Sorry, I couldn’t find it, it seems even I just remember that this is how it should be done and these are the reasons, but I can’t find in my library where did it actually come from.

8 – Programatically render field widget inside dialog

I created a custom email field with a widget that has about 4 form elements inside (textfield, text area, checkbox). The UI becomes very messy when I add this field with unlimited cardinality to a custom entity.

My Requirements
(1) I need to have a link show on main UI (instead of the widget form with the “Add another item”. This link should open up the field widget form inside a dialog when clicked and values entered should be saveable to the entity on which the field is attached.
(2) I will use a table element to show the list of values of this custom field already added to the entity. This table should be updated with the newly added value after I add the new field in the dialog box.

What I Know
I know how to generate a link with “use-ajax” class to display the target in a dialog. What url to put in the link that will show the custom field’s widget form in the dialog is what I’m scratching my head…

Someone pls point me in right direction?
Thanks.