|
Kevin Marois wrote: It wouldn't be so bad if they created an option to change it an defaulted it to the previous setting,
You know the problem with that is that the code would be buggy, and every once in a while, in a completely random fashion, it would just ignore your selection.
Or it'd reset it again to the selection you don't want during the next update. Then eventually you'd just give up.
Sounds familiar?
|
|
|
|
|
I think it really is that the bar has dropped and so you have even people at the vaunted msft working on VS who can't actually make a more productive contribution than that. ^ > is what someone can do, so ^ > is what we get.
|
|
|
|
|
Because they are more interested in form than function, and to "be more inclusive."
Squares, apparently, hurt people's feelings...
|
|
|
|
|
LOL - A more liberal IDE 
In theory, theory and practice are the same. But in practice, they never are.”
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
|
|
|
|
|
What do you mean whitespace, eh?
|
|
|
|
|
Maybe they do it to reduce confusion. A squared + is a plus, but a squared - is also a plus. 
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
trønderen wrote: Maybe they do it to reduce confusion.
They failed.
In theory, theory and practice are the same. But in practice, they never are.”
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
|
|
|
|
|
Ahh you must be putting the square around the - using CSS.
|
|
|
|
|
Because they can and you can not.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I thought it appeared different but only now know why. C’est La Vie[^]
|
|
|
|
|
Perhaps MS should make these icons configurable. Config files are as old as eternity, isn't it?
Or, has MS already made these icons configurable ?
|
|
|
|
|
|
Some f$€k3r has a useless job and needs to justify their paycheck.
Do they know we developers work mostly on muscle memory and instant pattern recognition? Mess that up and it's like cutting off our dominant hand. That's why we go to war with each other over code formatting after all.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
The shortest horror story: On Error Resume Next
|
|
|
|
|
Well said
In theory, theory and practice are the same. But in practice, they never are.”
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
|
|
|
|
|
If you wish to format a date in Power Apps, there is a nice set of format letters to provide custom output. So using the Text function I can write
Text(myDate, "mmm dd yy")
Or for time I can write
Text(myTime, "hhmm")
Or I can combine them into
Text(myDateTime, "hhmm mmm dd yy")
Why would anyone think to use the same lower case letters for two very distinct fields?
There is actually a work-around, make sure dd comes first in the date. Good luck 'mercans.
|
|
|
|
|
Because "mm" means minutes, and "mmm" means the three-letter short month name. If you want the two-digit month number, you use "MM".
Custom date and time format strings - .NET | Microsoft Learn[^]
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I wouldn't necessarily assume that Power Apps use the same conventions .NET does.
I've used Power BI just a tiny bit, and I wouldn't assume anything based on any prior knowledge or...dare I say, common sense.
|
|
|
|
|
No, you use lower case "m" for both.
|
|
|
|
|
I thought 'mmm' meant Beer. At least it does when Homer does it.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
I’m begging you for the benefit of everyone, don’t be STUPID.
|
|
|
|
|
Richard MacCutchan wrote:
There is actually a work-around, make sure dd comes first in the date. Good luck 'mercans. Big Grin |
I would make sure dd comes last. yyyy-mm-dd is my default format.
|
|
|
|
|
|
Richard MacCutchan wrote: Why would anyone think to use the same lower case letters for two very distinct fields?
Maybe they really like Campbell’s Soup?
Their slogan used to be Mmm Mmm Good.
Jeremy Falcon
|
|
|
|
|
I tried to make a struct with two fields named mm and mmm respectively. The compiler accepted it without any warning. Confusing, isn't it?
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
What if they need the minutes, then the three letter month, then the minutes again, then the two digit numeric month?
We won't ask why, but hypothetically speaking...
|
|
|
|
|
Doesn't PowerApps know whether it is formatting a time object or a date object? That would surprise me a lot.
If I were to develop a formatting function, and was told "No no - you can't use that character to indicate a certain formatting - it has been used to format a very distinct field in a another value type", then I would scream out in protest. I cannot let the format strings for "my" type be limited by the format strings for all other types!
That being said: Doing detail formatting of times and dates is blatant anti-internationalization, an explicit effort to make it difficult to adapt you solution to other markets, an invitation for customers outside your own locale to misunderstand or not understand the data you output. Don't do that! Use locale dependent formatting, and stop fiddling around with literal format strings!
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
