I won’t get into how annoying Windows can be about accounts and permissions. That’s more of a book than a quick blog post. But if you used your Microsoft account to login to your Windows 10 Pro computer and you want to use remote desktop from another computer to login…this is for you:
on your host PC (the one you want to control remotely) – login using your Microsoft account and your password. do not use any other login method. from the login screen select the option to use your password. you must use your password.
on your host PC enable remote desktop by opening the start menu and searching for remote desktop settings
on your client PC, open your start menu and search for remote desktop connection
enter the computer name or IP address and press connect
when prompted for your login, use MicrosoftAccount\<your email address>
What is Phaser 3? It’s a nice game engine for web browsers you can download for free here: https://phaser.io
How do you get VS Code to show Phaser documentation automatically in the editor? Create a text file named jsconfig.json in the root of your project folder that includes the Phaser types and your game code. The root of your project must contain folders that contain the code for Phaser and your game. For example, if your project folder is named “myProjectFolder” and your game code is stored in a folder called “src” and the Phaser 3 code is stored in a folder called “phaser” then here is your directory structure and jsconfig.json file’s contents:
After you create the jsconfig.json file and have saved it, close VS Code. The next time you open VS Code, select File->Open Folder and select your project root (“myProjectFolder” from our example”) and the Phaser information will be available after a short loading process completes.
Click Add someone else to this PC to create a new user. Select “I don’t have an account” so that the user will be local only. After creating the user, click the name and Change Account Type, then select Administrator
Today I had a nice chat with someone named Hana using the Drift chat window on the website. They wanted to know more about how to use the Telnet connect to a VLC media player.
The good news is that I was able to find the information they needed. I did have to git clone the VLC source code and search through the Lua modules for the command they needed so it took about 30 minutes to find the answer.
The bad news is that the email address they gave me isn’t working so they can’t receive the invoice for my time or the answer to their question. Hopefully they were able to find the answer on their own.
If anyone else needs help finding an answer about a piece of software, network, or programming challenge, feel free to ask! I am happy to help with what I know and can even help find the answers I don’t know.
I am so impressed by the people who designed and developed the TheoryBoard. They launched a successful Kickstarter campaign and they not only delivered, but they really increased the value of their product by taking it from prototype to production while adding features and refinements all along the way.
I was able to quickly connect the TheoryBoard to my MacBook Pro, open Cubase, and begin recording. The USB cable is all you need if you are using a PC or Mac. I did test it with both external power and USB power only. It works really well!
Since I didn’t watch the tutorial yet, here is me just exploring a little. 🙂
What I like: – plug and play – excellent build quality – plays chords and scales that sound great without any knowledge of music theory – light weight and easy to carry – non-slip base – pressure-sensitive lighted buttons
What can be improved:
– the symbols for the central display buttons that affect the current scale are not documented in the boxed literature or within the menu system, I’ll have to go online to learn more
– the lighted buttons are pressure-sensitive but require some finesse that I don’t yet have. Sometimes I was able to get the results I desired but there were also times where the result was louder or quieter than expected. Changing the algorithm used for debouncing these inputs might be able to improve this
– the central display indicates when a button is pressed but the lighted buttons themselves do not, it’s personal preference, but I’d like the button I press to dim or turn off for a moment so I know the press was registered there as well
I love this MIDI instrument. My only concern is that I won’t get used to the somewhat finicky response of the lighted buttons. Again, that might be user error, but it definitely has room for improvement. This has been a great first user experience and the bonus of following along with the development of this product has made this a great Kickstarter experience as well.
I’ll try to post again after I have had enough time to really learn how to use this instrument, but if you have the chance to pick one up sooner then I highly recommend you do!
The only way to override the default shortcuts while the QTextEdit has focus is to intercept the QEvent::ShortcutOverride event. There are 2 ways to intercept this event: 1. write an event filter 2. subclass QTextEdit and then override the virtual event(QEvent* event) method. I prefer this 2nd method (pun intended) because anything that changes the functionality of a widget should probably be its own class.
Here is an example of how I block the QTextEdit from using all shortcuts that start with Ctrl being pressed: