Prototyping does not work with local Turnkey - mdriven

Please see the model in attachment.
I started prototyping with it. It does work with XML-Persistance, SQL and MDriven-Server, but not with local Turnkey.
Repro: Start Prototyping -> Seekers -> Action Person Seeker -> add some new Persons with New Person -> Select one -> Show Person -> try to set Father or Mother with "Set" Button. Nothing happens. In other kinds of Prototyping the Seeker is called, and you can select a person and set it as Father or Mother.
See also Screenshot
Efim

It turns out that your actions that will be triggered by the buttons was opted out:
You could discover this reason by checking browser console:
console.warn("A button action that tried to bring up a modal window did not find the backing action: " + navigate.ActionName);

Related

Testing keyboard input for blueprint select with react testing library

I have created a codesandbox to illustrate my issue here:
https://codesandbox.io/s/floral-resonance-z2h43?file=/src/SelectExample.spec.tsx
I am trying to test the keyboard navigation within a blueprint select. That is opening the select by clicking the button, then pressing key arrows untill the desired item is active and confirming with enter which closes the select.
The functionality works perfectly fine.
I however fail to get the unit test(s) to work. As you can see in the linked sandbox a unit test that select the new item via mouseclick works.
I however have run out of ideas how to trigger the onChange of the SelectExample with keyboard inputs.
userEvent.keyboard() doesn't work and fireEvent doesn't either (though I'm not sure what to target considering how blueprint implements the select and that I can only add data-testid to some elements, but going to any number of parentElements from the items which have testids didn't work either). Same issue with userevent.type(), unless the target for that is the desired item in which case the test pases but only because the implementation type() clicks on it before entering its text.
References for the keyboard input:
https://testing-library.com/docs/dom-testing-library/api-events/
https://testing-library.com/docs/ecosystem-user-event/
I'd appreciate any input.

How do I add a column with a new status in Jira?

I've modified the board and added a column in Jira but there are no status for it and it doesn't show on the board, how to fix and have the new column show up on the board and work correctly ?
This has confused me several times so I'm documenting the steps here.
Go to Board Settings
Click on columns
Click 'Add column' to add the new column - Code Review in my case
You will notice however that the board say
This column will not show on the board without a status
You may also notice that the min/max values cannot be entered
So you (think) next go to Issue Types...
WRONG !
Actually you want to go to
Workflows
You'll see a workflow called something like Software Simplified Workflow for Project [..].
Click on the Actions edit link (the pen symbol)
Now you will be presented with a diagram showing the status'.
Click + Add status and add the new status, e.g. Code Review
Make sure you allow transitions from the other status (it is unchecked by default, so you should usually check it)
It is when you fail to do this that you can run into the 'can't drop ticket into column problem'
Next select the status category. Code Review was obviously "in-progress".
This allows for automatic ticket status transitions.
Arrange the new diagram to reflect the new status (this is for appearance in the diagram only).
Finally the last step is that you have to publish the change ('draft')
Now you can see the "unmapped status"
and you can move them into then new column
When you do all this, finally you can reload the board and see the new status!
Whew !!!

My click trigger always fire in google tag manager

I'm having difficulties using the Click trigger in google tag manager.
I want to setup a trigger to fire on a click event, only when the element class contain "scrollto".
But the thing is, it keeps firing up even when the "scrollto" class isn't part of the element I clicked on.
Here are a few screenshot I hope will help you understand the problem:
Thank you for your help,
Alexis
Ones you set up any click trigger you will get these events everytime a user makes a click but that doesnt mean the trigger it self is being fired. You can append the trigger to any tag and you ll see that if you click anywhere else the tag wont fire even when you see the event.
Hope it helps!
Instead of click classes contains scrollto,
Give click classes equals scrollto

Prevent users from typing and clicking in MS Word Add-in

I am writting a MS Word Add-in, I create a button to run a long time work with text. My work requires that during the time it is excuted, no change can be made by user ( typing, clicking, deleting ...) When this work is completed, user can type and click as usual.
I have used
this.Application.Options.AllowClickAndTypeMouse = false;
However, this doesn't work.
Who can help me!
First, your approach is wrong. The Click and Type is Word functionality and has nothing to do with disabling user Mouse clicks
(For more information about Click and Type refer to here).
Now for your question, here is one approach I would suggest:
If the user is not able to do any action, I would expect an appropriate message, so my idea is to create a modal form by using:
myForm.ShowDialog();
It should do the job and block the active document until it get closed.
I would also add a nice progress bar and "Close" button which you will enable when work has done.

Lifecycle and Activity Stack

In the application activities are stacked like this: A - > B - > C - > D - > E.
If I receive a particular notification and click on it, Activity E is started.
If I then click back (button on phone or button on actionbar), the application exit.
How do I make the transition to Activity D in this case, and then back through C, B, and A?
My code of back button:
public boolean onOptionsItemSelected(MenuItem item) {
switch (item.getItemId()) {
case android.R.id.home:
finish();
break;
}
return true;
}
Everything is okay when starting the application normally. The problem is when Activity starts from the notification.
Android has the functionality you're after built in, and it is already well documented. To begin with you should look at the TaskStackBuilder class. It was introduced in JellyBean, but is already included in the support library, and you use it to build a synthetic TaskStack which is what you need. A summary from the documentation reads:
When crossing from one task stack to another post-Android 3.0, the application should synthesize a back stack/history for the new task so that the user may navigate out of the new task and back to the Launcher by repeated presses of the back key. Back key presses should not navigate across task stacks.
TaskStackBuilder provides a way to obey the correct conventions around cross-task navigation.
How you build it is going to depend on the relationships of the Activities in your app, but the Tasks and Back Stack developers guide is a good read to help you decide, as is the Navigating with Up and Back design guide, if this is all new to you.
You'll find some code examples in the Implementing Effective Navigation lessons, also on the Android developers site, in the training section.
Incidentally, the button on the ActionBar is referred to as Up. Even though it sometimes shares the same functionality as the back button, the two are not the same (I assume that's the one you are talking about ;-) .)
I think you can solve your problem by sending an intent from Activity E to Activity D, and so on.
Therefore you should overwrite the method
onBackPressed()
that is called when you click on the back button.