I am making a message receiver application from mqtt with the famous itoo extension. For the code block I have a little difficulty, when the notification comes in. I want to make it when pressed open the browser to see the news that I convey. it runs when screen1 is open, but not when closed.
forgive my language if it is not right, because I use translate. I am new and I am from Indonesia. Please give instructions, masters
Error in Itoo1.NotificationIcon block: the block literally does not accept string type blocks. You can avoid this by storing the string to a variable then feeding to the block but that ends up in a runtime error.
Hi, I am trying to read multiple machines. When I do this with my app, the app gets blocked until the reading of all machines is finished. That's why I'm trying to use 'Background Task' to implement something like a BackgroundWorker as in 'Visual Studio.net'. Initially, I tried to create a Background Task to get familiar with it. So far, the app does what it's supposed to, but I still have some questions.
I pass addresses to the task and receive the responses from the BroadcastEvent. Is that correct? Although it works, I'm not sure if it's correct or if it's just working by chance.
I receive a notification from the green circled block. Why? I don't need this notification. Can I suppress it?
It is not possible to suppress it unless you use the Create Task block instead of Create Process (which can only run your service for a few minutes).
I dont get the idea of what you are trying to do? Why do you want to store something, pass it on to the background service and get it back? I dont get whats happening nor what you want to do.
You may be confusing the extension with asynchronous operations or simply new-thread operations? Am I right? Because this extension, background tasks, is just to run tasks in background even while the app is turned off.
So you want to listen to all of the components that run in the background?
Currently the extension does not offer Any Event since generally limited number of components are used in background. And their events needs to be manually registered.
Hey, yea sorry for the late reply, but to just give some context I'm using the phone Call component to allow me to catch the number of incoming calls, the regular component incoming call event would only trigger with a specific number, the "any phoneCall" variant would trigger the event with any phone number calling, and would also return the phone number as a variable, I am looking to do this in the background, I've managed to get itoo to register regular events like clock1.Timer, but not something like clock.Timer / any clock.Timer. Which as u said is probably, because the extension doesn't support it. So yea thanks a lot for informing me!
Edit: Wait a second , I might've been mistaken about the phone call component, I just decided to go through the documentation one more time, and apparently yea the regular event does trigger with any phone number, which means I don't need to use an any phone call component, I can't believe I didn't catch this even though I've been using the phone call component for quite a long time now . This means that I should just be able to get by using the regular event, I'll go ahead and test things out, and see if everything works fine with this piece of information.
Edit2: Seems like I still can't get the event to trigger in the background, well here are my blocks that relate to the background process, I just can't figure out what's wrong.
Okay!! I'll be sure to try out the Notifier.LogInfo method, and also to answer your question the JmlPhoneCall is an extension that allows you to answer or cancel incoming phone calls, here's a link to the thread where I got the extension!
Edit: I went ahead and managed to get the notifier and logcat working, no changes tho on getting the event to trigger, I would say tho that having that the show alert method is still more convenient for this simple use case as I am still just testing in UI, and am not really needing any detailed logging information.
I also included the screen inisilisation block in this screenshot
Well fair enough , but in this case I'm pretty sure the foreground service still runs while I have the app open, so the event should trigger, and show the UI popup in app, and as for outside the app, I wouldn't really need something like a log since if the event does get triggered(which is during a phoneCall), the CallAccept method/function would be triggered, and it would accept the call, and I'd know that yes indeed the event got triggered, the notifier is just a little extra tid bit of info that might serve itself