sirspot.com

^\s*VarType_t[^\*]+var\;

This means find the variable named “var” of type “VarType_t”

The variable must be defined on its own line because the ^\s* means find the line that starts with zero or more blank spaces or tabs.

The variable cannot be a pointer because the type is followed by [^\*]+ which means match any character except for ‘*’ one or more times

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:

1. 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.
2. on your host PC enable remote desktop by opening the start menu and searching for remote desktop settings
3. on your client PC, open your start menu and search for remote desktop connection
4. enter the computer name or IP address and press connect
5. when prompted for your login, use MicrosoftAccount\<your email address>
6. enter your Microsoft password and it should work.

Good luck!

What is VS Code? It’s a nice text editor you can download for free here:
https://code.visualstudio.com

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:

myProjectFolder/
myProjectFolder/jsconfig.json
myProjectFolder/phaser
myProjectFolder/src

{
  "include": [
    "src/*"
  ],
  "files": [
    "phaser/types/phaser.d.ts"
  ]
}

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.

Good luck!

Open Settings ->Accounts

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

Open regedit

Create this DWORD and set the value to 1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system\LocalAccountTokenFilterPolicy

I’ll make this quick

Open Windows PowerShell and enter the following command

Get-NetConnectionProfile

Find the InterfaceIndex of the network you want to change to private. Use your number for the next command. I’ll use 26:

Set-NetConnectionProfile -InterfaceIndex 26 -NetworkCategory Private

Done

Want to try a pre alpha of a program that generates C/C++ code for enums?

Mac OSX
Enum Maker 3000 v1.0.0
https://1drv.ms/u/s!AoyivGDoGjLGgosulIDh3JlERr9XSQ?e=fuW7fD

Windows 64bit
Enum Maker 3000 v1.0.1 (slightly improved!)
https://1drv.ms/u/s!AoyivGDoGjLGgowsXFWRiXxvu-c5_A?e=w7rFnP

Please let me know if it runs on your machine and if you have any comments. Thanks!

Here it is!

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

Take aways:

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!

Have you even received the following error after adding Qt to your Visual Studio project? The fix is easy but not what you would expect.

MSVCRTD.lib(exe_winmain.obj) : error LNK2019: unresolved external symbol WinMain referenced in function “int __cdecl invoke_main(void)” (?invoke_main@@YAHXZ)

To fix it, Open Properties for the project then go to Linker -> System and change the SubSystem to Not Set from the drop down list. Make sure you do this for All Configurations.

That’s it. Back to work!

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:

bool CustomTextEdit::event(QEvent *event)
{
    if(event->type() == QEvent::ShortcutOverride)
    {
        QKeyEvent* keyEvent = static_cast<QKeyEvent*>(event);
        if(keyEvent->modifiers().testFlag(Qt::ControlModifier) == true)
        {
            // allow override of all Ctrl+ shortcuts
            return false;
        }
    }

    // normal procedure
    return this->QTextEdit::event(event);
}

Now that the QEvent::ShortcutOverride event has been used to cancel the shortcut, a QAction can be used to capture the shortcut calling setShortcut with the QKeySequence you wish to use. For example:

this->m_ActionCustomUndo->setShortcut(QKeySequence("Ctrl+Z"));

You can also setup the action directly in Qt Designer like this: