Sometimes some tasks can be taken a lot of time to end up.
This code is created in order to play a random radio music in background while the script is running another task until to finish up and the music will stop too.
The code is working well, just i'm waiting for any suggestion to improve th...
> DeclarationType.Enumeration was explicitly excluded, along with DeclarationType.UserDefinedType. Now I can see why a UDT would need to be excluded, but not an enum. Removing the exclusion fixes the issue.
**Description** Rubberduck Code Inspections works fine on Excel 2016. Tested on my backup which was made prior to installing MS Office Pro 2019. Under Excel 2019
> Since this error appears in the form section, which we do not evaluate anyway (We just have to parse it to get to the actual module.), I would like to suggest to just patch up the parser rule for the forms part with an additional alternative INTEGER COMMA INTEGER. That should work around the issue that apparently forms can be saved with different regional settings, in contrast to the actual VBA code.
> I think we can work around this issue by first trying to get the name from the filename and only getting it from the caption if the document is not saved. In that case, the name should usually not be too long.
> An alternate potential solution would be to determine if the width of the displayed string would extend off the edge of the CE and self-truncate with an elipsis ....
> I'm sure it would be really helpful if you would ensure logging is set to TRACE level (Rubberduck | Settings | General Settings | Minimum Log Level = Trace), recreate the problem, and post the log.
Should this be reported as a bug Warning: Member 'Sort' was not found on the compile-time interface for type 'ArrayList'. - (Utils) Utils.HelperForVBIde, line 89 Warning: Member 'toarray' was not found on the compile-time interface for type 'ArrayList'. - (Utils) Utils.HelperForVBIde, line 91 In practise .Sort and .ToArray (.toarray) are working just fine.
@MathieuGuindon. So I just found out. No worries the code works fine. I can even browse the values in ArrayList which is something I haven't yet worked out how to do with my C# kvp wrapper for dictionaries.
Rubberduck version 2.4.1.4627 Operating System: Microsoft Windows NT 10.0.17763.0 x64 Host Product: Microsoft Office x64 Host Version: 16.0.11929.20300 Host Executable: EXCEL.EXE;
**Description**
"Quick Fixes" when applied through the _Code Inspections_ window always result in a "Quick Fix Application Failure" even when the fix was seemingly applied sucessfully
**To Reproduce** Steps to reproduce the behavior: 1. In a new Excel workbo
> Build .4627 is fairly old. You may want to try the latest build available (.4945 as of this moment) because I've not experienced anything like that in my memory.
> Build .4627 is fairly old. You may want to try the latest build available (.4945 as of this moment) because I've not experienced anything like that in my memory.
> Note: Rubberduck's installer does not delete user settings, so if AC is disabled, it will remain disabled even after a version-upgrade install. This is by design and expected.
OK, issue 5157 got me looking at the inspections, and I've got this one in the module I tested: 'Case' block contains no executable statements. I get that - it is valid in this case. My question, what's the recommended way to do this:
Case vbext_ComponentType.vbext_ct_ActiveXDesigner
Case vbext_ComponentType.vbext_ct_Document
ToFileExtension = ".cls"
when it's entirely intentional?
throw a comment in there that they both get the same ToFileExtension to avoid the confusion?
I've got a RecordInserted and a RecordUpdated column in my table, both declared datetime.
I keep writing WHERE RecordInserted = '2019-10-01' and getting nothing back because they all have times associated with them. What I need is WHERE CAST(RecordInserted as date) = '2019-10-01' instead. Is there a simple way of "auto-converting" that that is recommended?
I keep looking at my table wondering "Where's mah datas????"
I don't really think I need the time associated, so I could convert from datetime to date in the table itself...
@FreeMan well, I always write my expression like so... WHERE foo >= @date AND foo < DATEADD(DAY, 1, @date) (assuming @date is a date --- if it's a datetime, then CAST(... AS date) is needed to avoiding timevalue mucking up the show)
@this so basically "shoot yourself in the foot often enough, eventually you'll remember not to"... These aren't sprocs or anything, just quick queries. I have very few datetime columns (some date, some time but very few with both), so I guess it's just a learning curve
@FreeMan not sure I got it through.... I always write that way... regardless of whether I'm querying a date or datetime
Defensive coding saves lives!
If you only have to remember one form that works for every circumstance, that automatically avoids any dumb WTF moments like you just experienced earlier with the simple = @date
IT: Navigate here and clear the cache.
Iven: There is no cache to be cleared. The requisite program hasn't been installed.
IT: I am guessing clearing the cache did not work?
Iven: :sends-photo-of-printed-screenshot-circling-evidence-of-no-cache-directory-in-red-marker: This is what I mean.
hmm. I fear that might heavily penalize those that uses Print method.
I do not know about VB6 projects -- @mansellan or @MathieuGuindon might have a better idea of how common those are. In Access reports, I've seen some use abuse that. Fortunately, it's quite rare.
why can't Print be treated like an ordinary method name? That should be a problem for the resolver, not the parser, no?
haven't looked at the grammar recently but is PRINT distinct from a simple name expression, right? We are not connecting it to the Debug faux-whatever-it-is, right?
Anyway if it's true that we cannot even use Print as a ordinary method, then the stupid library with Print (and not implementing the IVBPrint interface) will never work anyway, and we can force it to be like a keyword and take precedence over the unrestricted member name.... right?
[Test]
public void TestStringFunction()
{
string code = @"
Sub Test()
a = String(5, ""a"")
End Sub";
var parseResult = Parse(code);
AssertTree(parseResult.Item1, parseResult.Item2, "//lExpression");
}
That cannot work, because String is a built-in type.
expression :
// Literal Expression has to come before lExpression, otherwise it'll be classified as simple name expression instead.
//The same holds for Built-in Type Expression.
whiteSpace? LPAREN whiteSpace? expression whiteSpace? RPAREN # parenthesizedExpr
| TYPEOF whiteSpace expression # typeofexpr // To make the grammar SLL, the type-of-is-expression is actually the child of an IS relational op.
VBA Rubberducking
VBA Rubberducking