Mercurial > public > ostc4

view RefPrj/RTE/.project @ 210:b2a9e9b02df0 cv-persistent

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
New feature: make selected customviews persistent Add the set of selected customviews during dive time to the persistent settings. Nothing has changed to the menu, so a user still has to access the on/off page from the simulator or during an actual dive, but once changed here, the settings are preserved for later dives. It feels a bit as waste of menu space to add a second page for something that is already available. And further, I have to admit the adding a page is rather complex to get the navigation right, so that is a 2nd argument not to add a page. Further, getting this one setting saved to the persist preferences is a bit of a hack. Misused an existing global bool value (WriteSettings) to force a actual write despite not being in surface mode. Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
author Jan Mulder <jlmulder@xs4all.nl>
date Tue, 26 Mar 2019 13:00:15 +0100
parents d24395f7c939
children
line wrap: on
line source

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
	<name>OSTC4_RTE</name>
	<comment></comment>
	<projects>
	</projects>
	<buildSpec>
		<buildCommand>
			<name>org.eclipse.cdt.managedbuilder.core.genmakebuilder</name>
			<triggers>clean,full,incremental,</triggers>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.cdt.managedbuilder.core.ScannerConfigBuilder</name>
			<triggers>full,incremental,</triggers>
			<arguments>
			</arguments>
		</buildCommand>
	</buildSpec>
	<natures>
		<nature>org.eclipse.cdt.core.cnature</nature>
		<nature>org.eclipse.cdt.managedbuilder.core.managedBuildNature</nature>
		<nature>org.eclipse.cdt.managedbuilder.core.ScannerConfigNature</nature>
		<nature>fr.ac6.mcu.ide.core.MCUProjectNature</nature>
		<nature>fr.ac6.mcu.ide.core.MCUSingleCoreProjectNature</nature>
	</natures>
	<linkedResources>
		<link>
			<name>Common</name>
			<type>2</type>
			<locationURI>OSTC4/Common</locationURI>
		</link>
		<link>
			<name>Small_CPU</name>
			<type>2</type>
			<locationURI>OSTC4/Small_CPU</locationURI>
		</link>
	</linkedResources>
	<variableList>
		<variable>
			<name>OSTC4</name>
			<value>$%7BWORKSPACE_LOC%7D/ostc4</value>
		</variable>
	</variableList>
</projectDescription>