Thanksgiving lighting took a holiday

[tunnus]

Just noticed that when trying to reorder some expressions, e.g. move the most recent one from the bottom of the list to the first, this new order didn't "stick".

At first yes, but when visiting some other menus (obviously saving before that) and then coming back, the moved item was in its original position (in the end of the list).

I currently have 29 global expressions (which may or may not have some relevance to this problem). Using build 21281 on linux.

Can log a PR with logs, if this seems hard to reproduce.

[tunnus]

Anyone noticed the same?

[toggledbits]

So far, I haven't been able to reproduce this. It would not be a logs thing, because it's on the UI (the logs only log the server activity, and don't often provide much help in troubleshooting UI/interaction issues). You might open the JavaScript console in your browser (and which browser would that be?) and see if the browser is showing any errors there.

[tunnus]

@toggledbits using Chrome (94.0.4606.81) on macOS (Big Sur). Saw two errors that happened already before editing the order of expressions. Tested with build 21286

[toggledbits]

Neither of those errors is relevant. The first isn't even from any part of the UI, looks like browser internal, and the second is from inside the Bootstrap package and also not relevant. Is this from after edit but before save? If so, do the save and see if anything is logged by the save operation.

[tunnus]

@toggledbits before edit & after save

[toggledbits]

Wait... wut? That makes no sense. Let's try this again. Open the JavaScript console. Go into the Global Expressions editor. Move something to another position, then hit Save. Then report if any errors were logged.

[LibraSun]

I'm getting a slightly different effect with Expressions, under latest-21292-ac02d68, namely when I visit my list of existing Globals and drag one to the top of the list, then click SAVE and go visit elsewhere in the UI... upon returning to Expressions, that item now appears at the very bottom of the list. I haven't watched for browser errors in the monitor yet, just wanted to report this anomaly.

UPDATE: More generally, even if I drag an existing expression anywhere in the ordered list, and click SAVE, the topmost item seems always to hop to the bottom of the list. Grabbed these screen shots to illustrate:
BEFORE (after dragging 'sun' to the 2nd position from top)
AFTER (following SAVE, leaving 'Expressions' then returning)

At that point, 'Timestamp' had been bumped to the bottom of the list.

[tunnus]

@librasun this is exactly the same behaviour I’m experiencing

@toggledbits did another test with console open, no errors

[toggledbits]

OK. @LibraSun 's description was a bit more concise, so I was able to find that issue. Next build tomorrow.

[tunnus]

@toggledbits I’m good at finding bugs, but bad at explaining them

[toggledbits]

@tunnus Sometimes it takes teamwork to get things through my thick skull, too.

[wmarcolin]

@librasun looks like you have some interesting expressions, like this one at the timestamp

Can you share the full screen for us to look at? And of course use good ideas

And your last comment is very good, we can find each other, but to reproduce and explain is another story

[toggledbits]

Just a note, @LibraSun 's timeStamp expression was necessary before the addition of strftime() to the function catalog.

Link to Docs

[wmarcolin]

@toggledbits said in Ordering of global expressions:

strftime()

Master sorry for the ignorance of your apprentice, can't this strftime() function be used this way?

I am getting an error.

[toggledbits]

@wmarcolin Grasshopper, the arguments for strftime() are described in the reading thus:

strftime( format_string [, time ] ) — Formats time to a human-readable form controlled by format_string. If time is not given or null, the current time is used.

It should be clear from this that the first argument is to be a string containing the formatting codes. A string is a sequence of characters enclosed in quotes. You are missing the quotes.

[wmarcolin]

@toggledbits

[toggledbits]

@wmarcolin

[LibraSun]

Yeah, most of my more intricate Globals originated from the Before Times, and would not be applicable today. Anything worth sharing I created long ago as workarounds, for which Patrick probably has since added features to accommodate.

[tunnus]

@toggledbits just to confirm/check, that this fix (on ordering of expressions) is included in 21294?