Nicholas Martin
Nicholas Martin
Just to add to this, I've been using Puppeteer for my functional tests and it has the following: ```js await page.setRequestInterception(true); page.on('request', interceptedRequest => { if (interceptedRequest.url().endsWith('.png') || interceptedRequest.url().endsWith('.jpg')) interceptedRequest.abort();...
As mentioned in #853, the above suggests an `EventEmitter` and not a lifecycle hook as intended. The solution could be to create a single generic hook, similar to `afterPrune` or...
@malept #509 doesn't resolve the issue raise here. For one, `start` / `complete` are unnecessary as this is inferred just by it's execution, and what is suggested for progress is...
Even though this isn't merged in, it came in handy!
Please let me know if you could suggest better methods.
Just realised a better way to query a connected devicetype would be this: `Chroma.Instance.Headset.Connected`
@brandonscott That is true. For keyboards you may still have to query which device it is. However, lets say you separate out the logic per device type, or simply want...
Also, if you wanted keyboard device specific code, you would currently have to do something like this: ``` C# function Connected(DeviceInfo d){ return c.Query(d).Connected; } if(Connected(Razer.Devices.Blackwidow)){ // Do something }else...
Ok, so having created a new method for listing the connected devices, which is just a simple `List()`, seems we should also add the Device Name to DeviceInfo.
Or at least attach the Guid.