I edited epoc.ini
added textshell in the first line.
When I run from the emulator:
NO window border is shown when I run.
It prints directly to the screen, so I can't interact with it
and the console window is isolated from the emulator window
I'm runninbg Windows 7 with Screen Resolution 1280*780
Instead of running textshell and get all this headache , just run the normal emulator and run the eshell from it, and type the name of your console application to run it.
Related
For me the the behaviour of Android regarding the lifetime of an application is something mysterious. Specifically:
I start qPython and run a script. This script launches a thread that runs in the background.
If I exit the qPython interpreter by clicking the "back" arrow several times, the qPython window disappears. However, this does not seem to mean that qPython is stopped, as when I display the active windows by clicking the "square" key, the qPython window is still there, and if I select it it shows qPython in the last state I saw it before hitting "back".
Apparently, when the active windows are shown, if I drag the qPython thumbnail out of the screen, the thread running in the background is killed.
Question 1: should I infer that dragging the thumbnail of qPython off screen kills an app, including its background threads?
It happens to me to restart qPython and launch the script while a previous instance is already running. I then get errors because of conflicting access to the same resources.
Question 2: is there a way to know that a previous instance is running, so that my code can show an explicit message and prevent a resource conflict?
I am creating calculator VBO in blueprism object studio.
In application modeller I gave calc.exe path and able to launch calculator, but I am not getting identify option to spy on any element..
In Element, After clicking Launch buttion, identify is appearing for a split of sec and Launch button is coming back instead of Identify
PS- As mentioned in videos and links, I have launched calc via application modeller not directly via windows..
I am using windows 10, BluePrism V.5.0.11.0 versionenter image description here
Windows 10 calculator is complicated case, please consider using different application in your training. For example paint is much simpler to get started.
If you really need to get that going, then you may need to launch application first, using one object, and afterwards use second object to attach and interact with it.
can be two reasons
1. Either your application is not launched properly.
2. Sometimes we face problems with some versions of applications.
The best way to fix your problem is
Edit your settings remove the application path from the navigate stage.
Launch the application separately
Open Navigate stage > Action > Attach
Provide the window title within quotes (example: "Calculator")
Click OK then run the object
Now if you go to application modeller
You will be able to see the identify button under the element.
Hope this will help you.
I resolved this by unchecking "Disable invasive techniques (hooking)".
The Windows 10 calculator runs with process name win32calc which is also located under c:\windows\system32.
So when you launch the application please make you identify the applications process name and its location
I resolved this by circumventing to windows 7 calculator instead of a windows 10 calculator on windows 10.
Link to download win 7 calculator for win 10-
https://winaero.com/download.php?view.1795
This will be installed in the same place as your default calculator.
Inside-
C:\Windows\System32
The name of the app in my case was "calc1.exe" to avoid collisions with the default calculator.
I used this as my base reference app for spying and it worked.
Also note, the hover to highlight button seems to be a bit buggy, try a bit hit and trail to get you required button to be highlighted and mark using "Ctrl+LeftClick"
I cannot find how to change behavior debugger window of IntellJ IDEA 2017.1.2 on Windows 10. I like to use it in unpinned mode, meaning it comes up when build happens (I execute it manually) and when I click on the edited file it goes down. But It does not take full width. It does not go over Project window as you can see in the picture below.
It works by default as I described on Windows 7. I mean it takes full width. Unfortunately, I cannot provide a screenshot about it. That machine is my workstation.
I cannot find in the documentation how to setup this. I assume it is due to Windows 10.
It's controlled by the Widescreen tool window layout option, disable it:
For some unknown reason, the react-native start command, while running for a while, opens an editor with the following message:
Opening ../node_modules/react-native/Libraries/Renderer/src/renderers/shared/stack/reconciler/ReactChildReconciler.js with vim
Not an issue (it still works), but more of an annoyance and I was wondering why it was doing this and that maybe it's a features I'm missing out, like stack traces after an error.
The editor opens when you click a line in the stack trace on the "red screen". Pretty easy to unknowingly do if you're running an emulator and are using the mouse to bring focus to it. It appears this is intended behavior (https://github.com/facebook/react-native/issues/6103)
You can work around it by using a launch line like EDITOR=true react-native start, while it will still "open an editor" that instantly exits, it wont break your shell.
I want to debug a today view extension (widget) in iOS 8, so I select the widget under "Scheme" in Xcode, and select my iPhone as the device and hit run. It says "running today-view on iPhone" and on the side bar on the left it says "Waiting to attach". It gets tuck at the "waiting to attach" phase forever and never shows me any debugging info on my iPhone. However this works fine if I select the simulator as my device. After a few seconds of "waiting to attach" in the simulator, the widget comes alive and debugging info is displayed.
Has anybody come across why an extension won't show debugging info on an iPhone but will in the simulator?
Do not stop & start the debugger while notification windows is open in the simulator. Close the notification window. Stop the debugger. Start it again. Debugging widget in iOS8 is very delicate. You need to do everything in a slow non-agressive way (for now).
Edit the extension scheme and make sure that under Run, the Executable option is set to Ask on Launch.
Run the extension scheme.
From the list, select the Today executable.
It should launch the Today app and your extension should be attached to the debugger now.
Close the notification window. It should start working.
I've been able to debug my Today view extensions in this way.
1) Make sure the notification center is dismissed.
2) Stop every process in Xcode with the stop button.
3) Run the extension scheme
4) Pull down the notification center and should hear the usual "app launched" sound from Xcode
5) Debugger will be attached automatically and you'll be able to debug the extension.
Let me know if this works for you.
This happened to me .... Looks like you were doing everything right .... try all the above.
The problem went away when I unplugged and re-plugged in my Phone.
Sometimes click on the widget will fire the running of extension.
Delete the app from your phone
Run the today widget scheme
It worked for me.