Good job this is in Hungarian, clears it right up
-
Presented without comment
-
capitalized_CamelUnderScore_Case FTL
But it's better than Button2
-
But it's better than Button2
Because it has Button (or an abbreviation thereof) twice, just in case you miss it?
-
In Java it would be:
secondMenuBtnClickHandler(...)
TRWTF is naming stuff by their position in the UI instead of:
saveAsMenuBtnClickHandler(...)
-
But this way it's extensible. If we need to swap the third and fourth buttons we only have to change all of the code instead of the archaic "moving it around in the visual editor" method
I joke of course. This code is set up so the visual editor shows a blank form. All of the button positioning is in code
-
Sounds like a fun (as in rip my eyes off) project.
-
It's pretty WTF heavy. Makes me appreciate just how clean the codebase and org structure was at my last job
-
In Java it would be:
secondMenuBtnClickHandler(...)</blockquote>
It probably wouldn't be named at all, what with anonymous inner classes (and lambdas these days).
-
You're right, it'd be
JWindow1$17$1.$_l()
. So much more debuggable thanButton1_Click()
.
-
Because it has "Menu" in it, so you know it's a menu button as opposed to a stand-alone button on the screen.
-
But it's better than Button2
In that the alphabetic ordering within the list of buttons provides that extra bit of "entertainment" for frustrated devs.
-
Does the UI of this project contain menus full of buttons? That could be an additional WTF...
-
Most non-consumer GUIs are steaming piles of WTF, usually because one jerkwad wants to see all the possible settings at once and the developers think that training can overcome just how enormously difficult their software is to use.
-
It's Windows Mobile 6. There's a 'fn' button on all screens that shows another screen with 8 other buttons, including the "get out of this menu" button which is called No-Op for some reason.
the developers think that training can overcome just how enormously difficult their software is to use
Sums this place up quite well
-
the "get out of this menu" button which is called No-Op for some reason.
Makes sense[1]. It dismisses the "fn" screen without actually performing an actual function.
[1] in the usual insane way.
-
Yeah, I guess cancel could be seen as "cancel the pending action on the main screen", and there's not a lot of space for descriptive labels.
-
including the "get out of this menu" button which is called No-Op for some reason.
You mean the one in the top-right corner of every WM6 window by default, which is "X" in normal windows and "ok" in dialog windows?
-
int[] _iArray = new int[2]; try { _iArray[0] = 238; _iArray[1] = 182; } finally { AdjustDataListBoxSize(_SomPanel._SomeCombiPanel.lbxMLScrollInfo, _iArray); }
I can only assume this used to be doing a lot more in the
try
. No idea what the magic numbers are forin the top-right corner of every WM6 window by default
Must have been intentionally removed in this product.
-
int[] _iArray = new int[2]; try { _iArray[0] = 238; _iArray[1] = 182; } finally { AdjustDataListBoxSize(_SomPanel._SomeCombiPanel.lbxMLScrollInfo, _iArray); }
@BuddyTFY