Lets you avoid if-statements that have trivial conditions and only affect visibility (ex.OK, so now that you've coded the 'gold standard' core of it, you need to figure out whether it it worth adding thin convenience-methods in the other style, to make life easier for whomever is going to use your object. Is it part of a domain model where expressing intent is important.There are a important side-effects or lots of logic being run, such as when the object has to check all of its containers for their visibility state, or triggers a transition animation.There is a lot of easily-shared code between showing and hiding.Your object is going to spend most of its time in a CRUD framework.It is just a simple bit-flip, or your object is mainly holding state.First you want to figure out which one is your 'main way', and focus on developing that: It depends on what showing and hiding means in the context. Consistency in APIs makes them considerably easier to learn and remember. Once you have multiple similar functions the setX() format generalises so you can have a set of consistent functions whereas the verbed approach spawns a host of functions that can be difficult to locate if you don't know what you're looking for.you can call setVisible(wantToSee) rather than using an if statement.

It's programmatically simpler whenever you're determining which state it should take in code, i.e.

To reverse setVisible(false) you call setVisible(true) whereas the opposite of hide() could easily be reveal().

It's immediately obvious what the inverse function is.

I think setVisible() should be preferred for these reasons: In languages which support properties, these should be preferred but since neither Java nor C++ do, I guess that's a moot point. Moreover, it's likely that you'll end up with a bunch of similar sounding functions/properties/whatever in your class and the multiplication of functions will further obscure which one goes with what. setEnabled, enable, disable) and thus this approach will end up with a much larger class interface. Whilst three functions instead of one may not seem like much bloat, remember that your class is likely to end up with many such functions (e.g.

I disagree with all posters suggesting multiple functions to do the same thing is a good thing.

Set visible android studio listview