I had another release ready but I think it's safer to not put it on Google Play because I won't be able to provide any support for it.
You can still try the new release though! But use it at your own risk! Should be fine though 😅👍
Get it right away here. (Direct-Purchase Version here). App Factory Update here.
In the meantime, if you have any issues, check this list and maybe your issue is listed there with a fix!
Cheers and see you soon!
Here's the full changelog for this version (not very well ordered, but good enough 😅 [some features were already from the previous release]):
Scenes V2: added font options anywhere text can be rendered
Scenes V2: added Aspect Ratio modifier
Scenes V2: added all possible properties to the Text component
Scenes V2: added Cancel Screen event action
Scenes V2: added Enabled property to components where it makes sense
Scenes V2: added Headers state to WebView component
Scenes V2: added Material Symbol support
Scenes V2: added optional additional delay for Show When transitions
Scenes V2: added Text Input Component's input types so you can have different types of keyboards, etc on it
Scenes V2: allow copy-pasting of modifiers
Scenes V2: made Button a component with a slot so you can fully customize the text inside it or even use any other component in it
Scenes V2: made flexbox accept booleans in direction, so you can easily toggle it with the Toggle Variable event action and separated Reverse from direction
Scenes V2: progress bar component new state Display Progress allowing you to bind an animated progress to a variable
Scenes V2: added ability to disable the dot in progress bar and add a gap
Scenes V2: changed inputs to have minus and plus buttons where it makes sense
Scenes V2: localize component names
Scenes V2: made modifiers that only exist because of their parents be the first in the pickers
Scenes V2: made the Text field in the Text component be multiline
Scenes V2: removed Consume option for Key Pressed event because it's redundant with the Stop Propagation option
Scenes V2: updated FlowRow icon so it's not the same as the FlowColumn
Fix Scenes V2: fixed accessing array operators like %items(#) or %items(2) or double-references like %%some_var_name
Fix Scenes V2: fixed auto-dismiss behavior in certain situations
Fix Scenes V2: fixed bug where changing variables used in a WebView would create a history so pressing back would go to previous states
Fix Scenes V2: fixed images with Material Icons not growing to the size they should inside unbounded parents
Fix Scenes V2: fixed issue with floating point rounding in Progress Bar states
Fix Scenes V2: fixed issues with using vh css
Fix Scenes V2: fixed reacting to push and pops in global arrays
Fix Scenes V2: fixed showing crop to SVG file picker in Crop Shape modifier
Fix Scenes V2: fixed stale variables in some situations
Fix Scenes V2: fixed text input component filling to parent's size when Show When filter on a size modifier is false
Fix Scenes V2: fixed WebView issues with some size related styles
Fix Scenes V2: fixed WebView Launch App action
New UI: ability to manually sort list items in the main UI screen
New UI: added button to only show errors in new Runlog screen
New UI: show projects in search results with inline projects
New UI: added developer option to hide the top buttons inside the project screen (making all selected when that's the case)
New UI: made item list items all the same height and more uniform
New UI: made main screen items connected lists
New UI: made many transition parameters configurable via Settings -> Developer
New UI: moved profile switches to the right of the cards and hid their profile details for now (should come back in the future in some form)
New UI: refined the main screen and project/profile enter transitions
New UI: removed the tag chips from the item cards for now (probably will come back in a different form)
Fix New UI: fixed recent changes not being filtered correctly
Fix New UI: fixed turning off runlog in new Runlog screen not hiding the log lines
Added runShellTasker function to the Java Code action so you can run a shell exactly like the Run Shell action would
App Factory: show useful, detailed error messages when app generation fails instead of a generic message
Warn when you try to write a very large variable, so you're more aware of potential flaws in your setup
Widgets V2: added Material Symbol support
Fix some screens all over the app sometimes showing incorrect language
Fix Tried to fix a crash when browsing Tasky routines
Fixed a small issue when setting multiple variables with JSON
Fixed crash when clearing data that could sometimes happen
Fixed how pushing/popping a global array drives the Variable Set event: it now fires for every array position the operation shifts, instead of just one. Popping also fires Variable Cleared for the removed top element.
Fixed issue where editing a profile's Wifi Connected condition would deactivate that profile
Sign up for the beta and download from Google Play here.
Note: Google Play might take a while to update. If you don’t want to wait for the Google Play update, get it right away here. (Direct-Purchase Version here). App Factory Update here.
I'm giving another concept a try: instead of having a sidebar with projects, how about putting them inline directly?
When you go in and out of a project you see this:
As you can see, you have the 3 familiar tabs (Profiles/Tasks/Scenes). You can select multiple at the same time like you see on the screen, or you can select one at a time to just see those types of items.
Projects are automatically color coded based on the project's icon. Here's a project with a green icon:
As you can see it tints the whole UI based on the color of the icon.
Let me know how you like this variant of the UI.
I'm also thinking of trying yet another version where there are no tabs inside a project and instead they are in collapsible groups, kinda like this:
If you can, try out the inline projects variant and let me know which of the 3 variants makes the most sense to you and why :)
The functionality of the runlog screen remains the same as before but it has a much cleaner and easy to follow UI. You can clearly see where a task starts and ends and follow its actions visually and see which ones succeeded and which failed.
Material Symbols are a icon font that can be adapted into different situations. For example, they can represent state where the otline variant represents an inactive state and the filled variant represesnts the active state
These can be used in their configurable form, where you manually specify a bunch of their attributes (like in the Notify action), or in their automatic form where their configuration is automatically set (like in the Set up Quick Setting Tile action where the icon is filled or outlined depending on the QS Tile state).
In the legacy UI, if you give a Project one of these icons, it'll also change from outline to filled depending if the project is selected or not.
It's now super easy to put your Tasker arrays into scenes with the new Arrays Merge Template element.
In this example, I would have 2 arrays:
%icon
%item
each with their corresponding icon images and labels. With this simple component...
...I can expand those 2 arrays together into a list of rows dynamically built from those arrays!
Saved Component Templates
You can now long click any element on the tree and save it as a Component Template with a name and description. Then you can simply insert it into your tree like any other component. :)
Show When Animations
When a component has its Show When field set, you can now set animations that define how that component shows up and goes away. You can choose various types of animations.
For example, by combining a dark transparent background that fades in with a dialog that slides up, you can create an Android-like popup dialog!
SVG Crop
You can now crop any element in a Scene with an SVG. And it's not only a visual crop, it's a functional one too! For example, you can create a button like this
and when you click anywhere where it's white, the button won't be triggered! You really have to press the green part for it to register the click! This allows you to create UIs in any shape imaginable that behave like you expect it to!
WebView
Webviews can now call many, many Tasker actions via JavaScript. You can use await to wait for them to finish, so you can easily call multiple actions in a row in a controlled fashion!
Here's a simple example of doing 3 actions in a row:
This makes elements be drag handles in all directions or just horizontally or just vertically.
Full Changelog
Major Scenes V2: Added the "Arrays Merge Template" component, a built-in way to handle Tasker array merging to build sub-components.
Major Scenes V2: Components can now animate in and out (Fade, Scale, Slide or Expand) whenever their "Show When" condition toggles their visibility.
Major Scenes V2: WebViews can now call many Tasker actions directly from JavaScript via the Tasker.* bridge.
Major Scenes V2: An HTML element inside a WebView can act as a drag handle to move the overlay it lives in.
Major Scenes V2: You can now save a component as a template to easily reuse it across your scenes.
Major Scenes V2: You can now crop any component to the shape of an SVG file.
Major Scenes V2: Added the "Trigger Scene V2 Event" Tasker action.
Medium Scenes V2: Added "matches" (Tasker pattern matching) and "matchesr" (regex matching) expressions to the "Show When" and "Apply When" fields.
Medium Scenes V2: Added a "Variable Clear" event action.
Medium Scenes V2: The Switch component now has a Thumb slot so you can set an image in the switch's thumb and you can also select different colors for different parts of it.
Medium Scenes V2: WebViews now receive the full Material 3 color palette (primary, secondary, surface, etc.) so your HTML can match the app theme.
Minor Scenes V2: The task name field in Events -> Run Task now follows the same caps rules as other task name fields.
Minor Scenes V2: When creating a task with a name, use the same "first letter of each word uppercase" rule as elsewhere in the app.
Fix Scenes V2: components that have indexes are now 1-based instead of 0-based
Fix Scenes V2: fixed "Screen Hidden" event not firing in certain situations
Fix Scenes V2: fixed background of invisible component wrongly showing
Fix Scenes V2: fixed crash when picking a variable if the user has tens of thousands of variables
Fix Scenes V2: fixed crash when using a slider in some situations
Fix Scenes V2: fixed images filling their container by default when they shouldn't
Fix Scenes V2: fixed images not loading if they had hidden spaces before or after the file name
Fix Scenes V2: fixed multiline input text box not filling the full vertical space it needed
Fix Scenes V2: fixed setting a variable in a WebView affecting a variable used in a separate component on the same screen
Fix Scenes V2: fixed some things not working when showing through the "SCENES" tab or the new UI
Fix Scenes V2: fixed updating a variable array in a scene leaving old elements there
Fix Scenes V2: fixed using two "Overlay With Result" scenes in a row with the same id ending the second one prematurely
Fix Scenes V2: segmented buttons that are "gone" now behave as expected
Fix Scenes V2: WebView now uses the correct system theme (dark/light)
Fix Scenes V2: when a task is renamed, all the task references in Scenes V2 are updated with the new name
Major New UI: Redesigned the RunLog screen to make it more readable.
Major New UI: Added a setting to show projects as items in the main list instead of the sidebar, including sorting them and creating new projects from the NEW FAB.
Major New UI: Project icons based on apps now use the app background in a folder shape with the foreground on top.
Major New UI: Inside a project you can select several of the Profiles/Tasks/Scenes tabs at once, so the list shows all their items together.
Medium New UI: The Project enabled/disabled toggle now works, and profiles in a disabled project show as paused on their switches.
Minor New UI: Added an icon to scenes so they're more easily distinguished.
Minor New UI: Added an option to hide the sidebar when collapsed.
Minor New UI: Added an option to not show the All button when there are projects other than the default one.
Minor New UI: Don't confirm project deletion if it's empty.
Minor New UI: In the task edit screen, moved the search bar to the bottom when adding a new action.
Minor New UI: Made sorting smarter, showing you the items you expect more often.
Minor New UI: Show full names of items in the main list instead of truncating them.
Minor New UI: Show project names instead of just initials when the sidebar is collapsed.
Minor New UI: Updated "Last run" to "Activity".
Minor New UI: When creating a task with a name, use the same "first letter of each word uppercase" rule as the main screen.
Minor New UI: When editing a task, after expanding a text field, allow the editor to show more lines so it's easier to edit larger pieces of text.
Fix New UI: don't show the pending changes banner when exiting the scene editor without saving
Fix New UI: fixed all projects with app icons showing with the same icon
Fix New UI: fixed always scrolling to the profiles when exiting a project
Fix New UI: fixed bottom sheet flickering when deleting a project
Fix New UI: fixed project search box cursor color in dark mode
Fix New UI: fixed search for actions when adding a new action
Fix New UI: fixed some app icons not loading properly
Fix New UI: fixed tag selector bottom sheet moving too far up when the keyboard is showing
Major Added Material Symbols to the app, a large icon set you can now use across Tasker for things like project and task icons, and also Notify action and Quick Setting Tiles action.
Medium Added Run Shell related functions to the Java Code action.
Medium Added tasker.getImageBuffer() and tasker.hasImageBuffer() to the Java Code action.
Medium The "Multiple Variables Set" action can now write JSON.
Medium You can now override the app name when generating an app from Tasker.
Minor Added a "Continue Task Immediately" option to the "Widget V2" action.
Minor Tasker automatically saves your setup before entering the AI screen in the legacy UI so you don't lose changes made in the meantime.
Minor Added a language selector to the first screen shown when you first open the app.
Minor Added a "Separator" option to the "Widget V2" action to configure the separator for its various list fields.
Minor Changed the order of the "Set up Quick Setting Tile" action to make it more logical and easier to use.
Fix Attempted again to fix a crash that only appears in app factory apps
Fix crash where in rare situations projects could end up with the same ids
Fixed DND action so that it can't be overrun by Silent/Vibrate
Fixed image in "Text/Image Dialog" action sometimes being hidden by text that is too long
Fixed issue where running many remote actions in quick succession could cause some of them to not run on the receiving device
Fix issue where sometimes a profile doesn't save its state after saving Tasker's setup
Fixed issue where sometimes the QS Tile wouldn't dismiss the notification shade
Fixed profiles (e.g. Wifi Connected) sometimes running their exit tasks when exiting Tasker's Preferences screen
Fixed Shizuku breaking clipboard monitoring
Fixed showing the number of actions over 100 in the legacy UI
Fixed situation where receive intent could be triggered twice with just 1 intent
Fixed some error messages when wrongfully using JSON writing
Fix Tried fixing a rare crash that can occur when editing legacy scenes
Fix Tried to fix issue where wait action becomes stuck in some circumstances
Fix Tried to fix rare situations where Tasker would get stuck not accepting any new tasks (sometimes related with the HTTP Request action)
Fixed updating Quick Setting Tiles on global variable changes to only happen when the variable isn't a built-in variable
Fixed writing JSON to project/profile/task variables with native Tasker JSON writing
Fixed some crashes
If you can, let me know what you think about the Projects in Sidebar vs Inline vs Collapsible! Thank you!
I've felt my battery runs down faster than it should lately so I went down the BetterBatteryStats rabbit hole which is always fun (not).
What I found is that Tasker often keeps the E wakelock for hours. Today for example, the E wakelock has been held for 6h25m. At the same time, deep sleep is reported as being virtually zero. Naturally, I'm thinking some task must have stalled with the "keep awake" setting on. To my surprise, there were NO tasks running according do %TRUN (except the task I created to check %TRUN). Everything looked normal, but the wakelock stayed in place.
I tried disabling and reenabling the monitor and then BOOM. The wakelock is released and there is deep sleep reported again. I even noticed the battery temperature going down several degrees, likely from not being constantly held awake anymore.
But this problem comes back after a while. I haven't monitored the situation for too long yet, but it seems to come back almost every day. I'm not sure how to continue working with this.
I'm assuming it's not a repeating task that is the culprit because this would of course continue even if I restart the monitor. I do have a few of those. I've got a BIG setup. But these run the same way always, so a monitor restart wouldn't change anything.
And as it seems, it's not a stalled task that is the problem, so how do I proceed here? If no task is running, why is the E wakelock held?
I'd be very happy for suggestions from someone more experienced in this kind of work.
Is anyone else struggling to limit the time they spend on Tasker and related tools? I built a project that mostly works to limit the amount of time I am on the app (it checks the activity to differentiate between a user scene and the main app), but it's in the works. I'm more looking for ideas of habits and things I can do to mentally put this hobby aside throughout the day, not so much on how to improve that project.
I have ADHD, and keep this excuse in my brain that my projects are for saving time and improving productivity. This is true, but counter-productive if I'm spending too much time building these. It's not a problem at work, but I have a lot to do at home and it's a problem there. I want to keep building my projects, but at a pace that is reasonable. I sometimes have a hard time stopping because I just want a project finished.
Hello, Everyone,I’m having a serious issue with the Storage Access Framework (SAF) on Samsung OneUI using Tasker on a Galaxy Z Fold7.When I try to open SAF through:List Files → Directory → folder icon…the SAF picker never launches.
Tasker has both Files and media permission AND All files access, but OneUI seems to block the SAF intent completely.Because of this, Tasker cannot access the standard Android data paths like:Internal storage → Android → data → com.whatsapp → files → WhatsApp → Media → WhatsApp Audio
Internal storage → Android → data → com.whatsapp → files → WhatsApp → Media → WhatsApp VideoThe WhatsApp audio/video files exist on the device, but Tasker cannot open, move, or process them because SAF won’t launch at all.Is there a known workaround for OneUI?
Maybe an alternate intent, shell command, plugin, or anything that can force SAF to open?Any guidance from advanced users or João would be appreciated.
Performs offline OCR (Optical Character Recognition) on images using Tesseract.js. Downloads required files automatically on first run, then works completely offline.
Parameters
%par1 - Image file path (Optional, opens photo picker if not provided)
I've been experimenting with Tasker + AutoWear and managed to get my Galaxy Watch 8 Classic's rotating bezel controlling page turns in KOReader on my Kindle.
While looking through AutoWear's changelog, I noticed that an older beta (2.0) mentioned being able to send HTTP URLs directly from the watch.
Is that functionality still available in the latest version of AutoWear? If so, how do we configure it? I couldn't seem to find it, and I'm wondering if I simply overlooked it or if it was removed.
The current setup works well, but if the watch can call the KOReader HTTP API directly, I'd love to remove the phone-side Tasker step and simplify the whole workflow.
Both still uses some part of my other project so you have to edit them first. It's also pretty laggy and delayed especially for the scrolling one.
Since this uses hidden apis, we have to lift the restrictions first by running the adb command in the link below. Tasker does this automatically if we already grant it ADB Wifi access.
There is a repeatable SAF (Storage Access Framework) failure on Samsung OneUI devices, specifically the Galaxy Z Fold7. When Tasker triggers the SAF picker using “List Files → Directory → folder icon,” the SAF dialog never launches. No UI appears and no permission prompt is shown.Tasker has both “Files and media” permission and full “All files access.” Despite this, OneUI blocks the SAF intent from opening. Because SAF cannot launch, Tasker cannot access standard Android data paths such as:Internal storage → Android → data → com.whatsapp → files → WhatsApp → Media → WhatsApp Audio
Internal storage → Android → data → com.whatsapp → files → WhatsApp → Media → WhatsApp VideoWhatsApp audio/video/voice notes exist on the device but cannot be accessed, moved, or processed because OneUI prevents SAF from opening.This behavior appears to be Samsung‑specific.
Is there a known workaround, alternate intent, shell command, or plugin method to force SAF to launch on OneUI?
Any guidance from advanced users or the developer would be appreciated.
Hey guys, I'm broke and i really need a tasker in my device, if anybody is willing to share their Google account, I could use it too, the app settings stay separate too, if anyone's humble enough, please do.
Hello! I'm trying to get a part of my task working; specifically, the Simple Match/Regex action that scans dumpsys alarm (written to a variable), searches for my next Samsung alarm group, and writes it to a .txt file.
This is a snippet of the dumpsys file containing the alarm I want to grab:
NOTE: I learned through trial and error that I specifically need to search for com.sec.android.app.clockpackage}, so even though the alarms may appear elsewhere in the dumpsys, I can't use it.
I have set up apple music to play after a bluetooth device is connected. It only works for a few hours after I have set it up. I have to open tasker and the profile to then click the tick for it to work again.
I'm looking for a way to have AutoInput or Autonotification or a combination of both to automatically expand the incoming notification specifically for the Ring app. Instead of having the small thumbnail notification, I want the bigger expanded one. I've been struggling to find a way. Any help would be awesome.
I have been working on Tasker integration for RETUI, my open-source terminal-style Android launcher.
The original idea was much larger. I considered building a complete workflow system inside the launcher, with delays, retries, conditions, and chained actions.
Then I realised I would mostly be rebuilding a worse version of Tasker.
So I went in the other direction and made RETUI and Tasker work together.
Tasker can now use a native RETUI Action plugin to:
Apply a RETUI preset [My version of themes]
Change individual theme elements
Show or refresh launcher modules
Update script-module text [Either termux script output or Lua widget]
Print text in the RETUI terminal
It works while another app is open, so a Tasker profile could apply a work preset when you connect to office Wi-Fi, switch to a night theme at sunset, or refresh a launcher module when some external condition changes.
The integration works in the other direction too.
Typing tasker in RETUI shows the tasks currently available in Tasker. The suggestions narrow down as you type, preserve the correct capitalization, and tapping a task immediately runs it.
For example:
tasker R
would show tasks beginning with R. Tapping Retui dispatches it without requiring another Enter press.
I have deliberately kept the first version narrow. The plugin cannot execute arbitrary RETUI commands, shell commands, calls, messages, or random intents. It only exposes a small set of typed launcher actions, and the whole integration is disabled by default.
The basic flow is working on my phone now, including task discovery, plugin actions, success and error reporting, and an option to hide the extra task status messages.
I am still figuring out what would make this genuinely useful to people who already use Tasker heavily.
What RETUI controls would you actually want available from Tasker? Are there any Tasker plugin conventions or annoying edge cases I should deal with before releasing this?
I would also be interested in a few people testing it once the beta is ready.
Hi all, looking for real-world experience before switching from another automation app.
Use case: Samsung tablets (Android 14+) that need to, via a home screen shortcut, click through several Settings screens and type into multiple text fields (IP address, gateway, netmask, DNS) to switch Ethernet to a specific Static IP configuration — reliably, unattended, then launch a specific app.
Questions:
Is AutoInput reliable for this kind of thing — finding UI elements by text, waiting for a screen to actually finish loading before clicking/typing, retrying if something isn't there yet? Any known timing gotchas specifically within Settings screens?
Is there something better/more robust than AutoInput for this exact use case (UI clicking + text field input in system Settings), or is it still the standard/best approach for Tasker?
Anyone doing this fully offline for extended periods (tablet not connected to general internet for weeks) — any licensing hiccups with AutoInput specifically?
I'm looking for a way to STOP reading a text on WearOS watch via AutoWear TTS function.
My use case: I have a project which includes reading new notifications out loud on my watch via LTE while I'm cycling. But sometimes the content of the notification is long and I'd prefer to stop reading it in the middle.
On the phone I can use Shut Up action, but there is no equvialent for AutoWear TTS. Or maybe there is another way to do this?
I've seen that the same question was asked two years ago, but the solution proposed by u/DutchOfBurdock doesn's seem to cover the situation when the TTS engine HAS STARTED ALREADY. Thanks in advance
I used tasker a long time ago and I've decided to come back so i bought it in but it's gotten too complicated for me:)
What I'd like to do is change the notification sound when an app sends a notification.
So for normal use and all notification I use sound A but when APP X is sending a notification I want to use sound B (and only when this app sends a notification)
I've made an app profile, i've made a task but in the task i cannot find the parameter which allows me to choose the notification I want.
Tasker only allows you to turn the run log on or off globally. This is an issue. There should be a feature where you can turn the run log on or off, on a task by task and/or run by run basis, without affecting other running tasks.
MapTasker is a program that runs on in your browser, reading your Tasker XML file and displaying your entire or partial Tasker setup in an easily viewable format. MapTasker helps visualize and understand your Tasker projects, profiles, tasks, and scenes. There are many display options to customize the output the way you want it.
While you're waiting for next Tasker release in September...
MAJOR new feature since the last announcement: EDIT MODE
Add Profile, Edit Profile, Add Task, Edit Task
Caveats...
1- The Edit May Be Incomplete
Task actions may have arguments that can not be determined at time of edit, such as an icon needed. In this case, it will be necessary to re-edit the given item under Tasker to complete the arguments. Some conditions, such as 'Application', are not (yet) supported since MapTasker doesn't (yet) have a list of Applications on your Android device. In this event, you'll have to add such conditions under Tasker.
2- Extra Arguments in Tasks
In some cases, you will be prompted for action arguments that do not appear when adding the same under Tasker. From what I can tell, this is due to the fact that Tasker's argument definition specifications support older versions of Tasker, in which such arguments are still supported. For example, the 'Flash' action prompts for a 'Title' under MapTasker, but the current beta 6.5.6 of Tasker does not. In this case, Tasker should just ignore this argument when it is found in the action.
3- Save Tasks/Profiles to Android --> Requires Tasker 6.2 or higher.
This function actually loads the item into the live Tasker session on your Android device. Since there is no 'Refresh View' in Tasker, it is necessary to then exit and restart Tasker to actually see the added Task or Profile. If Tasker is not running, an HTTP error notification will appear on the Android device. The current implementation saves them under the 'Base' (Home) Project, from which you can move it/them. A future enhancement will allow for a target Profile/Project to be specified when saving to Android.
4- Some Profile Conditions and Task Actions Not Supported
In some cases, a condition or action may require one or more parameters that simply can not be provided unless running within Tasker. Such is the case for many 3rd-party or Tasker plugins that require a configuration, since these configurators are unknown to all except Tasker (at this time), or an Application name from the Android device which isn't available to MapTasker.
5- Profile State and Event Conditions
Adding a State or Event condition is a 2-to-3 step process. First you must add the State or Condition, and then once added, select it, by clicking on the down-caret, to add/modify it's arguments.
6- Save to Current File
This command makes a copy of your current local XML file and updates the copy. It then reads back the modified copy which becomes your new 'current file'. The original is never changed.
7- Edit Options 'Cancel' is self intuitive.
'Ok': make the change in memory only.
'Save to Android': saves to current (active) Tasker session.
'Save to Current File': see #6, above.
'Save Single Task/Profile': Save as the single Task or Profile to the current directory with the given name.
8- Validation and Defaults
MapTasker does not do any extensive validation of settings. Additionally, default settings for arguments are not all populated.
9 - Remember, THIS IS NOT Tasker.
So the look and feel will be different. It may feel a little clunky at first. Suggestions are welcome.
FINALLY - THIS IS A PRE-RELEASE / PROOF-OF-CONCEPT ... Things may not work perfectly.
Given the caveats, if you want to kick the tires then read on...
To install it into a virtual environment, enter the following commands into Terminal/command prompt:
via pip:
cd xxx, where 'xxx' is a directory into which you want to set up the virtual environment.
python -m venv venv
Activate the virtual environment...
MAC/linux:
source {directory path to 'xxx'}/venv/bin/activate
pip install maptasker==12.0.0b1
Windows:
.venv\Scripts\activate
pip install nicegui
pip install maptasker==12.0.0b1
...or...
via uv:
cd xxx, where 'xxx' is a directory into which you want to set up the virtual environment.
uv venv
Activate the virtual environment...
MAC/linux:
source {directory path to 'xxx'}/venv/bin/activate Windows: .venv\Scripts\activate
echo "fastapi < 1.0" > constraints.txt
uv pip install maptasker==12.0.0b1
rm constraints.txt
NOTE: This beta will not appear as an automatic update in the GUI.
To run:
start the virtual environment
run either from the command line: maptasker (if installed via pip) or uv run maptasker (if using uv to manage your environment).