> Tag name (tag) - Optional. If not specified build tag or version is used. You can use environment variables in tag name, for example myproduct-v$(appveyor_build_version).
v2.1.0 is a lightweight tag
v.2.1.1 is not
v2.0.13 is
about every tag that's not from me is a lightweight tag
which is a bit of an annoyance, since it makes git describe essentially useless...
PSA: The ancient prereleases of versions prior to v2.2.0 have been deleted from the remote. If you have local copies of the tag, remember to delete them :)
for those of you that have a bash handy:
git tag -l | grep Rubberduck-v2.1 | xargs -n 1 --replace={} git tag -d {}
Reminder to self: Just write a damn JS or python script for it... github api exposes releases at https://api.github.com/repos/{owner}/{repo}/releases which can then be deleted via delete request
This class is used to make Excel Cells behave like Checkboxes. Clicking the cell raises a CheckedRange_Clicked(Target as Range) event and toggles it's value between 0 and -1. A combination of Fonts and Custom NumberFormats display the cell values as Checkboxes, Checkmarks, Yes/No, True/False or...
Hi gents, knowing that you are some really proven VBA and COM experts, I would like to ask you a question. In a Microsoft Access newsletter there was stated the thesis not to use such constructs:
Reports(<ReportName>).Requery
They say it would leave to a non dereferenced handle on the report object. They recommend that access to methods or properties via collections should therefore always be done with the interposition of an object variable and the corresponding dereferencing:
In very old versions of Access (like, 2.0? 97?) there was a reference counting bug where it was necessary to close. But that has been long ago fixed, and it related to the DAO object model, rather Access' but given that Access depends on DAO, I can see how that would also avoid the bug. So the question would be - when was that claim made?
Furthermore, it needs to come with a proof. If there really is a reference count bug, then it would be easy to prove - requery it 1000 times and watch the memory usage increase. If it never decreases, then you do have a memory leak.
@FreeMan: Unfortunately they don't seem to have a blog, but now I contacted them via their online survey regarding their newsletter. Will see if this helps.
but for foo& it's trying to coerce foo to Long so you're missing a concatenation, therefore it's an uncompileable statement so it highlights it in "error color"
Mildly annoying at times, but at least I understand the reasoning behind it now.
thanks, @MathieuGuindon
if he'd just get in the habit of properly formatting his code instead of lazily relying on the IDE to do it for him, it wouldn't be a problem to begin with
FWIW, it's not just the & - you'd get have similiar problems if you didn't have the space preceding the _ character, and it's not a type hint character (AFAIK).
> I am trying to use the code below, however I don't understand why it is printing out a blank message box? Additionally, there is only one for each day, and it is saying there is 2 files?
Now you can go on electronics.se and ask how long a cap in a PSU would stay charged, because you wanted to change a fan but some guy on the internet told you you might die.
^^ FWIW apparently I almost killed myself a few times there
considering that I had the PSU open at least four times (and am planning to open it for another time...
> Well, I know they can be dangerous from personal experience... Accidently tapped one with my finger while working in my case (bottom of PS drilled for 92mm fan, didn't have a fan in it yet), and it threw my arm 'bout as far back as my shoulder would let it go. Arm was numb and tingly for a couple of hours too. And yes, the computer had been unplugged for a while (15 minutes maybe).
> It's wise to discharge them. Don't short-circuit them right away, they don't like that. Discharge them across a resistor. The voltage will drop quickly at the begin, and then slower and slower. If the voltage has been reduced to a few tens of percent of the rated voltage you can short them to speed up the process. Short for some seconds, if you only short briefly the voltage will rise again if you remove the short.
Probably me conflating ideas. I remember hearing that you could in theory hang and swing on the power line without getting electrocuted -- birds do that all the time and can do so because they can't complete the circuit.
but thinking about it, that's not grounded.
(just don't touch the poles. Especially not if it's metal)
I'm completely with you on the double negations. Too often have I hopelessly confused myself with those. (Usually a truth table does the trick for me, if the case at hand is too tricky to sort it out in my mind.)
> The `While...Wend` construct was made obsolete with the introduction of `Do While...Loop` blocks, forever ago. Rubberduck should have an inspection that flags them, and a quickfix that replaces `While...Wend` with `Do While...Loop`.
> **Obsolete While...Wend loop** > 'While...Wend' loops cannot be prematurely exited without a 'GoTo' statement. Use the equivalent and more modern 'Do While...Loop' construct instead, which can be exited with an 'Exit Do' statement.
> Just to clarify - a first iteration/implementation of the inspection+quickfix can very well just flag While...Wend and replace with Do While...Loop without altering the rest of the code/logic. The rest is nice-to-have, cherry-on-top sugar.
The IT guy was making some changes to the thermostat system, and said they were tense, watched the systems like hawks, and had burn scars on their arms.
He sent a ridiculously high value through the thermostat to test it, and those guys leapt into action and had helicopters in the air and fire trucks rolling out from the prairie towns before he could say it was just a test.
He was like "I guess when a pipeline burns, it BURNS."
This class is used to make Excel Cells behave like Checkboxes. Clicking the cell raises a CheckedRange_Clicked(Target as Range) event and toggles it's value between 0 and -1. A combination of Fonts and Custom NumberFormats display the cell values as Checkboxes, Checkmarks, Yes/No, True/False or...
strTable = "SELECT ztblWork.jobnum, ztblWork.Grouping, ztblWork.PhaseNum, ztblWork.catNum, ztblWork.CostType, ztblWork.OriginalBudget, ztblWork.ChangeOrderBudget, ztblWork.PendingCOBudget, ztblWork.PresentBudget, ztblWork.ActualCosts, ztblWork.BudgetLeft, ztblWork.ThisWeek, ztblWork.HoursWeek " 
VBA Rubberducking
VBA Rubberducking