@Hosch250 let's them choose which warehouse things come from, and makes it easier to split up packages when one item is not available. planning for that in the foreground is a cost-saving measure
savings for amazon, not USPS/etc.
@Hosch250 that reminds me when my cousin mikey started delivering for UPS. he's typically a lumberjack/tree-cutter but it was really slow after cleaning up post-storms. anywho, his beard is covers all of his cheeks, like up to the cheekbone just below the eye. UPS told him he had to be clean-cut and presentable to wear their uniform. apparently customers regularly make comments. he got reprimanded and eventually let-go for not being clean-cut and failing to regularly tuck-in his shirt
which inherently makes me laugh because "clean-shaven" is now an illegal requirement.
trying to find the article on that; a black fellow sued his employer because he physically could not shave as shaving down to skin on the neck/face causes rashes and other health risks, which is apparently fairly common
google.com cannot be reached. well that's a fun error.
99.9999999999999999999999999999999999999999999999999% of the questions are from dabblers; always used option explicit... hell, turn that on as part of your options in the IDE so it does it FOR you
it's kinda like getting used to doing the dishes and putting them away right after a meal... may be a pain, but the benefits are real... keeps things neat and tidy
@theVBE-it'srightforme there is a LOT there to digest. I go back to it regularly are reread articles that it thought I understood... and realize I miss a lot
@Hosch250 niiiiiiice. that's a little better than ours; yesterday morning was 50 F, by dusk it was 17 F, getting down to 10 F with ~20 mph winds (feels like 5)
at least the sun is out to help?
better on a scale of shitty to shittier and your are paralax to the right threshold
24°F, feels like 24°. Hey... warmer in Fairbanks, AK thank it is here!! (26° there!)
@theVBE-it'srightforme in chat, if you hover over a message, a little arrow will appear to the right side of the message. click that one and your message will link to that one.
@theVBE-it'srightforme like this. Then when you hover over this message, you'll see which one it's in response to. Helps to keep threads somewhat untangled.
Also, when someone links to one of your posts, you'll get a notification icon over there <--- click that and it'll take you to the mention. Handy if you've been AFK.
@theVBE-it'srightforme is this a regular occurrence?
i'm still working on reading Clean Code. I've done a bit of skipping over chunks, e.g., the latter half of the forward, and just finished chapter 2. i guess it's always a good reminder to name appropriately, but reading and thinking about all of my laziness does help a bit and make me feel better about making appropriate changes to my laziness in the future... but maybe not all of it
i guess the one pro i feel best about is my hatred of l as a single letter (lowercase l) and i guess everyone else hates it, too... same as i don't use o (capital or lowercase) when using single letter variables (will try to not do that in the future)
i guess thanks @Hosch250 for getting me to actually pick up a book
@this command button; i have historically input everything that should happen when i press commandbutton1_click inside of the code for the userform. do you feel it would be more appropriate to put those into a standard module and application.run() in the userform code?
@Mast thanks man! our internet is having issues with certain domains so i can't use google to have checked myself... but i could get to reddit lol
I don't feel that a standard module is the best place, though.
Typically, I find that when I need to implement a common functionality, I implement something akin to a behavior.
Meaning, I create a class module, write a Init routine that takes a CommandButton as an argument, then in the form's code-behind, it instantiates the new class, then give its button to the class.
for my particular example, my UF has 2 comboboxes (list of currently open workbooks) so i can select source and destination workbook. the commandbutton dims src and dst workbooks and i start a slew of value=value as i loop through worksheets
Note that I've abstracted out the Validate - it's OK to use some other class or whatever to do the work, since the button is interactive and it should be assumed that classes don't get to be interactive but rather pass messages to the UI to do something.
um, yes, combobox is a class of itself but you'd have something like WorkbookDataSource class that would populate a given combobox. Then a WorkbookCopy class to do the actual copying between 2 given workbook.
> **What** Inspection Type: CodeQuality Helping ensure the code is explicitly stating the type.
**Why** Caught myself declaring a constant without including the type. This can have undesired side effects when using the const as a comparison in a RD unit test IE an `Integer` vs `Long` resulting in a type mismatch because of the oversight.
**Example** This code should trigger the inspection:
@Duga Forgive my half-baked possibly incomplete issue. In the middle of coding but still wanted to log this one. Apologies if it's already an inspection. Working with uncompilable code ATM ~.~
> If Thing implemented an ISomething interface, and we declared it like this:
1 Dim instance As ISomething 2 Set instance = New Thing We would still be looking at a Thing, however we would now be seeing it through the lens of its ISomething interface, and the members we would get in the drop-down list when we typed instance., would be the public members defined in the ISomething class module.
What error is thrown by that code if Thing does NOT implement an ISomething interface?
Hello fellow ducklings. I was wondering, at some point after 2007, does MSO migrate from the original VB6 form of VBA to something in the form of .Net..? What about that smog nonsense, MSO365..?
Doing alright. Found an exploit in a game, told the dev, he said good job thats quite the lucrative use of that ps i like that idea i'll nerf it by making it harder and then an update rolled out with the nerf and i still can do it
argumentModesFromSpecifier :: Int -> Maybe [ArgumentMode]
argumentModesFromSpecifier 0 = []
argumentModesFromSpecifier x
| x < 0 = Nothing
| otherwise = let argumentMode = toArgumentMode (x `mod` 10)
in case argumentMode of
Nothing -> Nothing
Just mode -> let furtherModes = argumentModesFromSpecifier (x `div` 10)
in case furtherModes of
Nothing -> Nothing
@Vogel612 As the local Haskell expert, is there a better way to do this?
:grumble: Trying to code when there is stateful access everywhere of a workbook is an impossible task to get correct.
> Tentatively got new feature request to work. :test test: Nope forgot about that. :test test: That doesn't work either :test test: Ooof that too :test test: Well FML this ain't never gonna work like they want.
VBA Rubberducking
VBA Rubberducking