-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dev master #35
Merged
Merged
Dev master #35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…icationError.xaml`. In `MainWindow.xaml`, a `d:DataContext` attribute was added to the main window to set the design-time data context to an instance of `ViewModel`. This change facilitates design-time data binding and aids in UI design when using the MVVM pattern. In `ApplicationError.xaml`, several modifications were made to the `TextBlock` elements. New `TextBlock` elements `MainError` and `Version` were added with various properties set. The `CallStack` `TextBlock` element was also modified, with changes to the `BlurRadius` and `Color` in its `DropShadowEffect`. The `Run` elements named `MainError` and `CallStack` were removed and replaced by the new `TextBlock` elements. List of changes: 1. `MainWindow.xaml`: Added `d:DataContext` attribute to the main window, setting the design-time data context to an instance of `ViewModel` for design-time data binding. 2. `ApplicationError.xaml`: - Added `MainError` and `Version` `TextBlock` elements with various properties set. - Modified `CallStack` `TextBlock` element, changing the `BlurRadius` from `10` to `5` and the `Color` from `#251153` to `#FF10178C` in its `DropShadowEffect`. - Removed `Run` elements named `MainError` and `CallStack` and several `LineBreak` elements, replacing them with the new `TextBlock` elements. 3. `ApplicationError.xaml.cs`: Set `Version.Text` property to `ViewModel.Instance.AppVersion.VersionNumber` in the constructor to display the application version number in the `Version` `TextBlock` in the `ApplicationError` dialog.
…amed "Version" from the `ApplicationError.xaml` file and the addition of a `StackPanel` to the same file. The `StackPanel` includes a button for checking updates and two `TextBlock` elements for displaying the current version number and a message about a new version. The `ApplicationError.xaml.cs` file was also updated with a new namespace and several new methods for handling updates and events. 1. The `TextBlock` named "Version" was removed from the `ApplicationError.xaml` file. This block was previously used to display the version number of the application. (Code Change: Removal of `TextBlock` "Version" in `ApplicationError.xaml`) 2. A `StackPanel` was added to the `ApplicationError.xaml` file. This panel includes a `Button` and two `TextBlock` elements. The button is used to check for updates, and the text blocks display the current version number and a message about a new version. The panel also includes a background with a linear gradient brush effect. (Code Change: Addition of `StackPanel` in `ApplicationError.xaml`) 3. The `ApplicationError.xaml.cs` file was updated to include a new namespace: `vrcosc_magicchatbox.DataAndSecurity`. (Code Change: Addition of new namespace in `ApplicationError.xaml.cs`) 4. The `Version.Text` line was removed from the `ApplicationError.xaml.cs` file, and the `DataContext` was set to `ViewModel.Instance`. (Code Change: Removal of `Version.Text` and setting `DataContext` to `ViewModel.Instance` in `ApplicationError.xaml.cs`) 5. Several new methods were added to the `ApplicationError.xaml.cs` file. These include `NewVersion_MouseUp`, which opens a web page with the application's releases if an update is not available, and `ManualUpdateCheckAsync`, which checks for updates. The `CheckUpdateBtnn_Click` method was also added to handle the click event of the new update button. (Code Change: Addition of new methods in `ApplicationError.xaml.cs`)
…lliChatModule.cs` which introduces a method for spelling and grammar checks using OpenAI and an enumeration of supported languages. The `OpenAIModule.cs` was also modified to allow public setting of the `OpenAIClient` property. The user interface of the application was updated in `MainWindow.xaml` with new elements for spelling check and adjustments were made in `ApplicationError.xaml`. A new property `IntelliChatRequesting` was added in `ViewModel.cs`. List of changes: 1. The `DataController.cs` file was modified to remove a check for a status with the message 'BoiHanny' or 'Gun'. 2. A new file `IntelliChatModule.cs` was added. This file contains a class `IntelliChatModule` that has a method `PerformSpellingAndGrammarCheckAsync` which uses OpenAI to perform spelling and grammar checks on a given text. It also contains an enum `SupportedIntelliChatLanguage` listing various languages. 3. The `OpenAIModule.cs` file was modified to change the `OpenAIClient` property from private set to public set. 4. A new image `SpellingCheck.png` was added to the project resources in `MagicChatbox.csproj`. 5. The `MainWindow.xaml` file was updated with several UI changes including adding a new border, a new text block, and a new button for spelling check. The DataContext was also updated. 6. The `MainWindow.xaml.cs` file was modified to remove the OpenAI import and add a new method `SpellingCheck_Click` to handle the click event of the new spelling check button. 7. The `ApplicationError.xaml` file was updated with several UI changes including adjusting margins and font sizes. 8. A new property `IntelliChatRequesting` was added in `ViewModel.cs`.
… of the project version from 0.8.740 to 0.8.745. This suggests that there have been improvements, bug fixes, or new features added to the project. Changes: 1. Project version updated from 0.8.740 to 0.8.745. This could include minor bug fixes, performance improvements, or the addition of new features. Unfortunately, without specific details on the changes made between these versions, it's impossible to provide references to the code changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.