|
Interesting exercise (best on a VM):
Install Chrome/Vivaldi and make it the default browser.
Then open File Explorer and go to: C:\Program Files (x86)\Microsoft\Edge\Application and rename msedge.exe (I named it msedge.exe.FO)
See what works and what doesn't.
>64
It’s weird being the same age as old people. Live every day like it is your last; one day, it will be.
|
|
|
|
|
In July.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
Last time I tried something like that (it wasn't Edge but I had the same idea), some Windows monitoring component undid that after a while, if not the next reboot.
|
|
|
|
|
Is it just me or is it time developers stopped adding those annoying GOT IT? popups everywhere. You're trying to use an app you've used a million times. You open it up, start diving in and..
Did you know you can change
the colour of the menu bar
to a slightly lighter shade of
purple!?!
[ Got it ]
And you can't do anything until you click "Got it". And then another pops up telling you that you can announce you can connect your spreadsheets to your social media account, and you can get notifications you don't want. And that they changed the menus to third-person plural.
I don't care, and you're stopping me from using the thing I'm paying for. And none of this is even vaguely important enough to stop me from doing anything until I acknowledge you.
Has anyone implemented these types of announcements, and if so, has there been a case where, in all honesty, it's important enough that someone acknowledges before they can do anything?
cheers
Chris Maunder
|
|
|
|
|
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣀⣀⣀⣀⡀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⡾⠋⠁⠀⠈⠙⠳⣦⡀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⡾⠋⠀⠀⠀⠀⠀⠀⠀⠈⢷⡄⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⡾⠋⠀⠀⣠⣴⠶⣦⡄⠀⠀⠀⠈⣿⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⡾⠋⠀⠀⣠⡾⠋⠀⠀⢈⡿⠀⠀⠀⢀⣿⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⡾⠋⠀⠀⣠⡾⠋⠀⠀⢀⣴⠟⠁⠀⠀⣠⡾⠃⠀⠀
⠀⠀⠀⠀⠀⠀⠀⣠⡾⠋⠀⠀⣠⡾⠋⠀⠀⢀⣴⠟⠁⠀⠀⣠⡾⠋⠀⠀⠀⠀
⠀⠀⠀⠀⠀⣠⡾⠋⠀⠀⣠⡾⠋⠀⠀⢀⣴⠟⠁⠀⠀⣠⡾⠋⠀⠀⠀⠀⠀⠀
⠀⠀⠀⣠⡾⠋⠀⠀⠀⠀⠉⠀⠀⢀⣴⠟⠁⠀⠀⣠⡾⠋⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⣾⠋⠀⠀⠀⠀⠀⠀⠀⢀⣴⠟⠁⠀⠀⣠⡾⠋⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⣿⡀⠀⠀⠀⠀⠀⢀⣴⠟⠁⠀⠀⣠⡾⠋⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠘⢷⣄⡀⠀⢀⣴⠟⠁⠀⠀⢠⡾⠋⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠈⠉⠉⠉⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ... It looks like you're writing a rant. Want some help?
|
|
|
|
|
Is there a hidden option to have the app not show these "helpful" tips?
/ravi
|
|
|
|
|
|
Did you know you cannot disable
these annoying Got it popups?
[ Got it ]
|
|
|
|
|
Chris Maunder wrote: you're stopping me from using the thing I'm paying for
I can see a solution.
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
|
|
|
|
|
We used to call them Tip of the Day. They were as annoying back then as they are now.
And CP may be complicit, as it's hosting at least one article that shows people exactly how to implement this. ![D'Oh! | :doh:](https://codeproject.global.ssl.fastly.net/script/Forums/Images/smiley_doh.gif)
|
|
|
|
|
It is not just you. I've been noticing this on everything from MS products to Adobe lately. Darned annoying "feature."
There are no solutions, only trade-offs. - Thomas Sowell
A day can really slip by when you're deliberately avoiding what you're supposed to do. - Calvin (Bill Watterson, Calvin & Hobbes)
|
|
|
|
|
Ahhh, brings back memories, what you are experiencing now, and the grand daddy of them all, was called "Clippy" - The Twisted Life of Clippy[^]
After banning and exiling poor Clippy came all of the other tweaks (children if you like) to get you involved in NOT doing what you are suppose to but to pay attention to our "super hero geeky pop-ups" like...
[Got It] ![Laugh | :laugh:](https://codeproject.freetls.fastly.net/script/Forums/Images/smiley_laugh.gif)
|
|
|
|
|
I'm working on a react project that has a component and related components named filter, filter group, etc. They need a complete overhaul and I was told to create a new set of components so that we can slowly implement the new one. Now I'm having the mental dilemma of figuring out what to name these new components. I flat out refuse "NewFilter" or "FilterNew" because you know it's going to have another iteration one day..."Filter2" seems blah. Does everyone else fret over naming things? What would you pick?
|
|
|
|
|
|
Ha ha...I was looking at thesaurus entries. I was almost considering "sieve" just to be fun.
|
|
|
|
|
Another choice is translate.google.com
Put the component name on the left and go through various languages on the right, you have
filter
in Lithuanian is filtras
in Igbo it's nyo
in Scots Gaelic it's criathradh
now you have the benefit of learning new languages while you program
![Smile | :)](https://codeproject.freetls.fastly.net/script/Forums/Images/smiley_smile.gif)
|
|
|
|
|
Chris Nicolatos wrote: in Lithuanian is filtras
in Igbo it's nyo
in Scots Gaelic it's criathradh
now you have the benefit of learning new languages while you program
What is it they say again about writing software as if the next guy that has to maintain it is a psychopath who knows your home address?
Yeah, that.
I don't see this as being any better than using random 2-character variable names. Or complete gobbledygook.
The smiley at the end of your post probably saved you. ![Smile | :)](https://codeproject.freetls.fastly.net/script/Forums/Images/smiley_smile.gif)
|
|
|
|
|
|
Ha ha.. looks like "CharlesFilter" wins?
That site is pretty sweet. Might actually use it once I put together more options.
|
|
|
|
|
I love !!!
I am working on a image file viewer thingy using Windows Imaging Components. I was going to call it WinCodecBitmap, but after spinning the wheel I think I will call it Hanna.
Thanks
Within you lies the power for good - Use it!
|
|
|
|
|
That's brilliant. I'm going to use these in our standups, 'cause our current order is by volunteer.
There are no solutions, only trade-offs. - Thomas Sowell
A day can really slip by when you're deliberately avoiding what you're supposed to do. - Calvin (Bill Watterson, Calvin & Hobbes)
|
|
|
|
|
I clicked on the link because it would be a programming revelation
YES I am still learning no revelations here keep moving
I now know better humor is worth more than revelations
made me laugh Caught Covid yesterday so needed a laugh
Chris Maunder2
|
|
|
|
|
the dreaded 'vid. Salt water gargle and netflix. I hope it brushes you lightly.
cheers
Chris Maunder
|
|
|
|
|
I put together the two suggestions (M-W thesaurus and wheel of names). I pasted the list of related words in wheel of names and a clairvoyant spin produced the right answer: WASH. Like in: if you don't know what to name it, it's a wash; any name is as good as the next.
Mircea
|
|
|
|
|
![Go to Parent](https://www.codeproject.com/App_Themes/CodeProject/Img/arrow-up24.png) Perfect task for Copilot.
I gave it the entire text of your original post and here is Copilot's response.
Copilot said: Ah, the eternal struggle of naming things in software development! It’s a challenge that many of us face, and it’s perfectly normal to fret over it. After all, a good name can make your code more readable and maintainable, while a poor one can lead to confusion and frustration.
Here are a few strategies you might consider when naming your new components:
Descriptive Names:
Aim for names that clearly convey the purpose or functionality of the component. For example:
FilterPanel: If your component handles filtering functionality.
FilterOptions: If it’s related to filter configuration.
FilterSelector: If it allows users to choose from different filters.
Think about what the component does and choose a name that reflects that.
Domain-Specific Terms:
Consider using terms from your project’s domain or industry. For instance:
TagCloud: If your component deals with tags.
SearchCriteria: If it represents search filters.
SortDropdown: If it handles sorting options.
Using domain-specific terms can make your code more intuitive for other developers.
Avoid Generic Names:
As you mentioned, names like “NewFilter” or “Filter2” aren’t very helpful. They lack specificity and might cause confusion down the road.
Instead, opt for more meaningful names that provide context.
Be Consistent:
If your existing components follow a certain naming convention (e.g., “FilterGroup”), try to maintain consistency.
Consistency makes it easier for developers to understand the relationships between components.
Avoid Abbreviations:
While abbreviations can save keystrokes, they often sacrifice clarity.
For example, prefer FilterConfiguration over FilterConfig.
Think About Future Iterations:
You’re right to consider future-proofing your names. Think about how the component might evolve.
Instead of “Filter2,” consider something like “AdvancedFilter” or “EnhancedFilter.”
Remember that there’s no one-size-fits-all answer, and different projects and teams have varying conventions. Ultimately, choose names that make sense in your specific context. And don’t worry—you’re not alone in this naming struggle! 😄
|
|
|
|