1
0
mirror of https://github.com/fadden/6502bench.git synced 2024-07-07 07:28:57 +00:00
6502bench/SourceGen/Res/Theme_Light.xaml

46 lines
2.2 KiB
Plaintext
Raw Normal View History

<!--
Copyright 2019 faddenSoft
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:local="clr-namespace:SourceGen.Res">
<!-- colors for ListView and ListViewItem (see CodeListItemStyle.xaml) -->
<SolidColorBrush x:Key="Brush_ListViewForeground" Color="Black"/>
<SolidColorBrush x:Key="Brush_ListViewBackground" Color="White"/>
ORG rework, part 6 Added support for non-addressable regions, which are useful for things like file headers stripped out by the system loader, or chunks that get loaded into non-addressable graphics RAM. Regions are specified with the "NA" address value. The code list displays the address field greyed out, starting from zero (which is kind of handy if you want to know the relative offset within the region). Putting labels in non-addressable regions doesn't make sense, but symbol resolution is complicated enough that we really only have two options: ignore the labels entirely, or allow them but warn of their presence. The problem isn't so much the label, which you could legitimately want to access from an extension script, but rather the references to them from code or data. So we keep the label and add a warning to the Messages list when we see a reference. Moved NON_ADDR constants to Address class. AddressMap now has a copy. This is awkward because Asm65 and CommonUtil don't share. Updated the asm code generators to understand NON_ADDR, and reworked the API so that Merlin and cc65 output is correct for nested regions. Address region changes are now noted in the anattribs array, which makes certain operations faster than checking the address map. It also fixes a failure to recognize mid-instruction region changes in the code analyzer. Tweaked handling of synthetic regions, which are non-addressable areas generated by the linear address map traversal to fill in any "holes". The address region editor now treats attempts to edit them as creation of a new region.
2021-10-01 01:07:21 +00:00
<SolidColorBrush x:Key="Brush_ListViewGreyText" Color="LightGray"/>
<Color x:Key="Color_HoverFill0">#FFF1FBFF</Color>
<Color x:Key="Color_HoverFill1">#FFD5F1FE</Color>
<Color x:Key="Color_SelectedFill0">#FFD9F4FF</Color>
<Color x:Key="Color_SelectedFill1">#FF9BDDFB</Color>
<Color x:Key="Color_SelectedInactiveFill0">#FFEEEDED</Color>
<Color x:Key="Color_SelectedInactiveFill1">#FFDDDDDD</Color>
<Color x:Key="Color_SelectedHoverFill0">#FFEAF9FF</Color>
<Color x:Key="Color_SelectedHoverFill1">#FFC9EDFD</Color>
<Color x:Key="Color_HighlightedCellFill0">#FFD9FFF4</Color>
<Color x:Key="Color_HighlightedCellFill1">#FF9BFBDD</Color>
<SolidColorBrush x:Key="Brush_MouseOverBorder" Color="#FFCCF0FF"/>
<SolidColorBrush x:Key="Brush_SelectedBorder" Color="#FF98DDFB"/> <!-- Color_SelectedFill1? -->
<SolidColorBrush x:Key="Brush_SelectedActiveBorder" Color="#FFCFCFCF"/>
<SolidColorBrush x:Key="Brush_SelectedMouseOverBorder" Color="#FF98DDFB"/> <!-- Color_SelectedFill1? -->
<SolidColorBrush x:Key="Brush_UpperHighlight" Color="#75FFFFFF"/>
<SolidColorBrush x:Key="Brush_SelectedUpperHighlight" Color="#40FFFFFF"/>
</ResourceDictionary>