On text entries in a v2 table widget: left/right alignment do nothing a colour such as #FF0000 causes the text not to show at all material colours such as primary do nothing

The following do work, and I assume others in the same groups do as well a number for font size cursive bold

This applies to Tasker 35.apk and 35-1.apk. I've requested beta access but an update has not arrived yet.

I love v2 Scenes - many many thanks.

So a task (Show) displays a V2 scene with various elements. There is a button with a Dismiss Scene event. After the Show Scene v2 statement, there is a Wait For Scene v2. All works fine, the values of the scene's elements can be access after the dismiss button is pressed, via variables.

I want to validate the scene's input before dismissing it, so change the Dismiss Scene event to a Run Task event.

I have several old profiles set up with Cell Near as a trigger, and have never had an issue with them until recently, when my evening profiles failed to trigger (the morning ones involving Cell Near triggered perfectly, and that was the last day any Cell Near profiles worked).

While troubleshooting, I realized that my carrier finally activated 5G Stand Alone (maybe part of the 2G/3G shutdown?). As a result, Tasker is unable to use Cell Near to scan these new cell IDs, the page remains blank even after scanning for 10+ minutes.

Does anyone know how to force Cell

If you have a horizontal row containing two vertical columns, only the first shows in the graphical part of the layout editor, and only the first shows when the scene is displayed. Please see attached screen shot.

If you show a v2 scene, wait for it with wait for scene result, and then show the original scene again, it either shows very briefly and then self dismisses, or it does not show at all.

A work around is to put a screen-id in the second show scene. Because of this simple work around, I think this is low priority. 

A value such as %myarray(%myindex) does not work when used as the text property of a Scene v2 element. This happens with text elements and Segmented button row elements, and probably others as well. 

Could the sliders (SeekBars) used by Tasker actions be improve or made customizable in settings? I find it impossible to use the press-and-drag method -- they just don't move, and the click method is very hit-and-miss.  Using the arrows is often impracticable when the value range is large since the arrows change the value by only +/-1.  Also in some cases a "logarithmic" (actually "exponential") scale would be more appropriate, e.g. for setting a Beep tone frequency where getting somthing in the middle of the audio spectrum on a linear scale that goes from ~0 to 16000 is extremely awkward.