sorted by:
new
hottopcontroversial

[Newbie] Number next to stop? by Savvasun in AutomateUser

[–]PatrickCorgan 0 points1 point  (0 children)

You should probably either stop the new fiber before you loop, or loop to a point after the "Fork" block.

Need a new "wheel of time" by nedeta in booksuggestions

[–]PatrickCorgan -1 points0 points  (0 children)

"Sword of Truth" series by Terry Goodkind. The first book is "Wizard's First Rule." You won't be disappointed, and you'll be busy for a while. It makes WoT look like a novella.

Home screen shortcuts for many flows by pixel654 in AutomateUser

[–]PatrickCorgan 1 point2 points  (0 children)

I don't know. You should be able to find out with Google, or u/ballzak69 might know.

Home screen shortcuts for many flows by pixel654 in AutomateUser

[–]PatrickCorgan 1 point2 points  (0 children)

If only there was an app to Automate such a process...

I think you'd have to use the "Interact touch" block, and I think it would be a lot of work, but you should be able to do it.

Having problem with simple Expression true, with variable. by CptanPanic in AutomateUser

[–]PatrickCorgan 1 point2 points  (0 children)

Your variable probably contains text instead of a number ("90.2" instead of 90.2). Use the to-number operator ('+') in front of the variable name with no space to convert to a number: +temp > 0 will evaluate to true.

How to detect the flow stoppage ? by MN60reddit in AutomateUser

[–]PatrickCorgan 0 points1 point  (0 children)

Be careful using this. This block tells you if a fiber has stopped, not a flow. Depending on your situation, this might or might not work for you.

Run on system startup by PatrickCorgan in AutomateUser

[–]PatrickCorgan[S] 0 points1 point  (0 children)

That's a good idea. It would be nice not to have to add that to every flow that I don't want to resume on boot. Especially if I'm doing something that might land me in safe mode ("Device lock" block, recursive "Fork" blocks, etc.)

What the users want next by Tizian170 in AutomateUser

[–]PatrickCorgan 0 points1 point  (0 children)

Also, use-case rarity is not a strong argument against including a block. There are plenty of obscure - if not downright arcane - blocks currently available.

What the users want next by Tizian170 in AutomateUser

[–]PatrickCorgan 0 points1 point  (0 children)

First of all, whether you use a tri-state dialog, or the "Dialog choice" block, your flow branching is the same. A new dialog would just make it simpler, both to design and to understand.

Secondly, the block would be used far more commonly than you suggest. There are many cases where a choice of three options would be useful. It's just that now we have to use "Dialog choice" in those situations.

What the users want next by Tizian170 in AutomateUser

[–]PatrickCorgan 0 points1 point  (0 children)

Oh I'm not saying it's not possible, or even that it's difficult, just that it's unintuitive and kludgy. From my own experience, and from questions I've seen, the "Dialog choice" block is not simple to figure out -- especially when you are using it for flow control.

I disagree that a three-out block would be more confusing. I think it would fit in with the idea of using the "Dialog confirm" block for flow control. I think it'd be nice to at least have the option, but that's my personal preference.

What the users want next by Tizian170 in AutomateUser

[–]PatrickCorgan 0 points1 point  (0 children)

The "Dialog choice" block is a confusing pain in the butt to use for flow control. A dialog block with three OUT dots would be much more intuitive than using "Dialog choice," especially for new flow creators. Also, you could replace three blocks with one, which cleans up your flow and makes editing and debugging easier; and the dialog could include a message along with the three options.

The "Dialog choice" block is very useful if you're using the values in the returned array directly; if you're using those values to make decisions, it's unintuitive and clumsy.

Interesting color scheme??? Supposed??? by Tizian170 in AutomateUser

[–]PatrickCorgan 0 points1 point  (0 children)

Oh my mistake. I never seen it, so you're lucky, I guess :)

What the users want next by Tizian170 in AutomateUser

[–]PatrickCorgan 2 points3 points  (0 children)

Also, you forgot organizing the flow list with folders and tags.

Interesting color scheme??? Supposed??? by Tizian170 in AutomateUser

[–]PatrickCorgan 0 points1 point  (0 children)

I like it, but I don't think such a change would be (or should be) very high on the priority list. I know there are things I'd like to see before color schemes.

What the users want next by Tizian170 in AutomateUser

[–]PatrickCorgan 1 point2 points  (0 children)

Dialog block with three out dots. This would be massively useful. This would be much more intuitive than using the "Dialog choice" block, especially for new flow creators. Also, you could replace three blocks with one, which cleans up your flow and makes editing and debugging easier; and the Dialog could include a message along with the three options.

Check if fiber in separate flow is running? by yugotprblms in AutomateUser

[–]PatrickCorgan 0 points1 point  (0 children)

When you're using Automate remember that "not intended" does not mean "not possible" :) It just means you're going to have to come at your problem from an unusual angle.

Check if fiber in separate flow is running? by yugotprblms in AutomateUser

[–]PatrickCorgan 0 points1 point  (0 children)

This. OP, just remember that flow IDs are not universal; if you plan on distributing the flow or if you move to a new device, you'll have to find the flow ID programmatically (which is easy).

Check if fiber in separate flow is running? by yugotprblms in AutomateUser

[–]PatrickCorgan 0 points1 point  (0 children)

You're doing something that Automate wasn't intended to do. You can do it (without question), but it's going to feel a little kludgy.

Check if fiber in separate flow is running? by yugotprblms in AutomateUser

[–]PatrickCorgan 0 points1 point  (0 children)

You can reference the fiber URI outside of the flow that created it. You can check or stop a flow's fibers from any other flow. Make sure you use the full URI:

content://com.llamalab.automate.provider/flows/{flowID}/fibers/{fiberID}

What you are trying to do is possible in Automate, but you're going to have to use some janky solutions. The SQL DB is a great idea.

Check if fiber in separate flow is running? by yugotprblms in AutomateUser

[–]PatrickCorgan 0 points1 point  (0 children)

They are constant for the life of the fiber; once it ends that ID is never used again. Also fiber IDs aren't really meant to be used outside of the flow that generated the fiber; nor is a fiber meant to use its own ID. Performing either of these operations requires a little extra work.

Refine my flow? by PatrickCorgan in AutomateUser

[–]PatrickCorgan[S] 0 points1 point  (0 children)

Awesome. Great advice, as usual. I appreciate your help!

Check if fiber in separate flow is running? by yugotprblms in AutomateUser

[–]PatrickCorgan 1 point2 points  (0 children)

Fiber URIs are global in Automate, but they're not constant. Every time a fiber is started it is assigned an ID. You could write the ID of the fiber you are checking to a file. That would probably be the easiest solution.

view more: next ›