Comments by M-Badger (Top 34 by date)

Does DATE(2024/04/13) evaluate to the same thing ?

What does that expression evaluate as ? Does it return a value that PowerBI recognises as a date ?

In the hardcoded version the month and the day seem to be reversed, it's DATE(Year, Month, Day) - hence DATE(2024,17,7) is the 7th day of the 17th month of the year 2024.
What is the format of [EndOfWeekDate] ?

You're not going to get far with that question, nobody is going to provide you with the code for a full reservation system.
Start by either
a) using an existing system (search for "open source seat reservation system"), there are several in existence
b) writing some code
c) using generative AI with a prompt such as "how can I create a movie theatre hall seat reservation system to reserve seats by number using php"; you won't get code for a complete application but you'll get a basic structure and then you can start putting it together

Then when you get stuck on a specific problem come back asking for help with solving it

Should the GetHashCode method have a 'return code' line or does the compiler know what to do with that ?

What overloads of the Render method exist ?
Do any of them take the types that you are calling with ?

What is the definition of the CreateStream method ?
What is its return type ?
Does that match the signature of the Render method ?

I think you need to be more specific, pick one aspect of the code that you think can be improved, post the code and why you think it needs work and you're more likely to get some feedback

It sounds like the changes it makes are therefore predictable even if they aren't as simple as 'change the top property of all controls by minus 10 pixels'. If you can predict them then you can reverse them with a simple piece of code to find all top properties and modify them appropriately.

Good to see you moving away from 2010 to a newer version that includes Yield in VB :-)
Good luck!

I am not sure what "instead of passing integer values I pass strings or dots" means, especially "dots".

The IEnumerable and IEnumerator are specific to the enumerable object in the IEnumerable class that you create so you can have an array of strings or any other type of object; you can have Lists, Colections etc. In your case you had a 1-dimensional array of integers so the code was written to that, if it was a 2-dimensional array or an array of double then the code would need to be adapted. I don't know if it possible to write equivalent late binding code to make it generic and I'm not going to try.

My answer showed you how to modify your "What have I tried?" code.

It may be my lack of ability but your C# does not make a lot of sense to me. For example you create a Range object and then instantiate it with a reference to 'this', so 'this' must be a Range object (a tuple of Index) and then you call the GetRanges method of that Range object but the Range class doesn't have a GetRanges method (nor for that matter does it have a SelectAll method). I wonder if 'this' is actually a string?

So assuming what you want is an array of range objects that indicate the start and end indexes of all occurrences of the search string within a larger string then, as the saying goes, I wouldn't start by trying to convert that C# code to a VB equivalent. Personally (not a professional) I'd create a List or a Collection of Range objects (if Collections/Lists were available in 2010) based on code that does the pattern matching and which populates the List/Collection. You then have an object which is enumerable. Or you can create an array of Range objects and implement IEnumerable/IEnumerator as shown.

It would be much more helpful if you included the code that you have tried

Thank you. I've updated the answer to reflect why I did that

I had assumed that the point was that I could have added that as a comment to the OP rather than as an answer, which wasn't unreasonable.
But thank you :-)

Have you tried -n+2 to check that it is not zero based ?

I think it may help if you assume I'm a rank amateur.
(I wonder if there is some confusion? I am looking at a library rather than an application, does that make a difference?)
Do you mean that it (and it would be only one) would work with a hidden color space, say CIE 1931 XYZ since it is the common reference, and that to obtain a model or a space, whichever is desired, this object would have methods that kick out a new object of the desired type? Presumably it could then construct itself on the basis of being given any color object, model or space - the reverse to the previous sentence and that perhaps the constructor could have an optional parameter of space, the default of which exposes the default space which is not directly accessible otherwise? How would you assign colors the model that it contains without specifying a model type and exposing its members, Red, Green and Blue for example?

Let's see if I've understood:
The classes, as conceived, don't think at all about actual drawing, they are just objects to manage colors, either color models or color spaces plus the conversions and the transitions between spaces and models (which is often confused). A color space being the manner in which a model becomes something real rather than abstract.

However, I think you are suggesting this:
A class called Color which contains as a member an interface, let's call it IColorModel.
The classes that manage the color models must implement IColorModel, RGB, CMYK etc.
The Color class should have a second member called IColorSpace which allows the model to be interpreted in such a way that it can be rendered correctly.
Color model conversions, e.g. RGB to CMYK, simply change the IColorModel member.
Color space changes, e.g. CIE 1931 XYZ to Adobe RGB change the IColorSpace member and have consequent changes on the IColorModel member, either a complete change or a change in the detail: CIELAB to sRGB would change both, Adobe RGB to sRGB would change the space and the detail of the model.
The ToGray methods, as an example, would call the relavant method of the IColor member which would probably also implement the IColorToGrey interface, both interface members pointing at the same actual object.

Have I understood anything?

aCMYK newColor = new aCMYK();
newColor.ToGrey(GreyScaleMethod.RedChannel)

Public Interface IToGrey
Sub ToGrey(ByRef color As IColorModelConvertible)
End Interface

Public Interface IColorModelConvertible
Function ToARGB(Optional ByVal alpha As Integer = 255) As aRGB
Function ToColor(Optional ByVal alpha As Integer = 255) As Color
Function ToAHSB() As aHSB
Function ToAHSL() As aHSL
Function ToACMYK() As aCMYK
Function ToHex(Optional ByVal alpha As Integer = 255) As String
End Interface

Public Class RGBAverage
Implements IToGrey
Public Sub ToGrey(ByRef color As IColorModelConvertible) Implements IToGrey.ToGrey
Dim newARGB As aRGB = color.ToARGB()
newRGB.Green = newRGB.Red()
newRGB.Blue = newRGB.Red()
color = newRGB.To [Help: Don't know original class type!)
End Sub

Out of interest (sorry for the delay) why custom rather than InvalidEnumArgumentException or ArgumentOutOfRangeException?
I get the idea / benefit of writing your own exceptions, however those two seem pretty well aligned with the problem at hand?

Struggled a bit to understand your articles, they are, at least as yet, a bit ahead of me - hopefully I'll get there sooner or later.
I did however find this: http://blogs.microsoft.co.il/blogs/gilf/archive/2009/11/22/applying-strategy-pattern-instead-of-using-switch-statements.aspx
I found it be a usefully simpler explanation for my level.

Thanks, I've started doing a thorough examination of how it works in a variety of circumstances.
My question here was linked to the one linked below and the implementation of a Switch...Case...Default
http://www.codeproject.com/Questions/639070/Exceptions-for-Enum-Method-Parameters

Thanks, I will keep this for futur e reference. In this case however it feels a bit like overkill since the chances of me inventing a significantly increased number of ways of converting colour to greyscale are limited (and hence changing the enumeration).

The switch remains ugly but 'more readable' (to me) than adding the code from your two articles.

Thanks, useful and straightforward. I guess I was wondering if the compiler added the relevant code to handle problems gracefully and informatively if, for example, someone passed in a typecast integer that was out of range. Or if it would throw a largely useless and informative error. The latter case, in my original thinking, would be the only justification for adding my own error..throw code, however...

You're second point is the same as that of RLH68? (his comment on my question). I'd forgotten to think of the error from both directions in either case.

For interest, which error type do you throw?

Can you show the code you have found and which you can't follow

There are lots of sources out there, as you have said.
Do you mean you don't understand the code they use?
Or that you don't fully understand the language used (presuming English isn't your first language)?

The obvious approach of taking each letter of the string and working away from it in both directions appears to be the least efficient (but it should be simple to code). Do you need to find 'better' answers?

You will need tom specify the question a bit more.

Do you mean how do you use the OpenFileDialog componenrt to open images?
Do you mean you want to set an image preoperty for a control (such as a PictureBox)
Or something else?

See the following answer.

You could argue that C# is hiding the behaviour that MSDN describes and that VB reveals in indirectly by doing 'weird' stuff. A win for VB.
Or you could say that C# is saying 'don't worry about what crazy stuff the compiler is going to do, I'll make you be sufficiently clear that it doesn't matter'.

A Win for C#. In some weird way the behaviour MS have chosen makes sense to me (maybe it goes back to having learnt procedural coding on a BBC Model B). Choice your posion and off you go, whatever you decide someone is gonna say 'brilliant' and right after someone else will say 'idiot'.

What was your expectation?