Support:Frequently Asked Questions (FAQ) - Revision history

Sascha at 13:34, 19 January 2023

2023-01-19T13:34:33Z

← Older revision		Revision as of 13:34, 19 January 2023
Line 366:		Line 366:
	the y increases towards the bottom. this is different from the mathematical sense.</b>		the y increases towards the bottom. this is different from the mathematical sense.</b>

			=== Q: Can Guiliani display data from a video-input? ===
			'''A:'''

			you can display data from a video-input in your GUI very easy.
			you will need:
			* a placeholder (GUIImage) to show the data in your GUI
			* a memory-region for the decoded data
			* an ImageID which will be bound to the GUIImage in your GUI
			* a function to decode a frame of video-data and refresh the memory and thus the image

			<syntaxhighlight>
			// global variables for easy access
			eC_UByte* pkMemory = NULL;
			ImageResource_t eImageID = DUMMY_IMAGE;
			CGUIImage* pkImageControl = NULL;
			eC_UByte ubBytes = 0;

			CMyGUI::CMyGUI(
			eC_Value x, eC_Value y,
			eC_Value width, eC_Value height,
			ObjectHandle_t eID) :
			CStreamRuntimeGUI(x, y, width, height, eID)
			{
			// Add application specific initialisation here if necessary
			...

			// get currently used screen format
			CGUICommonEnums::ImageType_t eScreenFormat = GETGFX.GetScreenFormat();

			// get bytes per pixel for buffer size
			ubBytes = ((eScreenFormat & 0xff000000) >> 24);

			// allocate destination memory for image data
			pkMemory = new eC_UByte[128 * 128 * ubBytes];
			memset(pkMemory, 0, 128 * 128 * ubBytes);

			// register dynamic image handle in guiliani with memory
			eImageID = GETRESMANAGER.RegisterDynamicImage(pkMemory, 128, 128, eScreenFormat);

			// create new image using this image
			pkImageControl = new CGUIImage(this, eC_FromInt(200), eC_FromInt(0), eC_FromInt(128), eC_FromInt(128), eImageID);

			// register timer with 100ms cycle to call CMyGUI::DoAnimate
			GETTIMER.AddAnimationCallback(100, this);
			}

			// also define in header file
			// virtual void DoAnimate(const eC_Value& vTimes);
			void CMyGUI::DoAnimate(const eC_Value& vTimes)
			{
			static char val = 0;
			if (NULL != pkMemory)
			{
			memset(pkMemory, val, 128 * 128 * ubBytes);

			GETRESMANAGER.RefreshImageResource(eImageID, pkMemory);
			val += 3;

			if (NULL != pkImageControl)
			pkImageControl->InvalidateArea();
			}
			}

			</syntaxhighlight>
	== Renesas ==		== Renesas ==

Administrator: Administrator moved page Support:FAQ to Support:Frequently Asked Questions (FAQ)

2021-09-23T13:28:13Z

Administrator moved page Support:FAQ to Support:Frequently Asked Questions (FAQ)

← Older revision		Revision as of 13:28, 23 September 2021
(No difference)

Sascha at 07:02, 21 June 2021

2021-06-21T07:02:33Z

← Older revision		Revision as of 07:02, 21 June 2021
Line 1:		Line 1:
	<metadesc>Frequently asked questions about the embedded GUI framework Guiliani.</metadesc>		<metadesc>Frequently asked questions about the embedded GUI framework Guiliani.</metadesc>

			== General ==

			=== Q: How should my application be structured? ===
			'''A:''' A typical Guiliani-application is divided into several parts, namely:
			* business-logic
			* frontend or GUI-code (includes CustomExtensions and other GUI-related objects)
			* GUI-project (created in the GSE)
			It has been a good practice for our customers to keep these three "layers" each with its own responsibility.
			* the business logic gets measured values or any other sensor data and instruments the GUI according to these
			* the GUI-code has the full control over the GUI and is responsible for updating the screen depending on the current state of the device (or what the business-logic has decided)
			* the GUI-project provides the assets and dialogs the GUI-code will use to handle all requests from the business-logic
			of course, the GUI-code can send back information or respond to any control request to the business-logic.
			By using this methodology you are able to separate all GUI-specific code from the business-logic (e.g. to be independent from the actual GUI-framework) only having a thin layer of abstraction.

			=== Q: Regarding documentation, what are the most important topics? ===
			'''A:''' In our online API-documentation, the following chapters contain valuable information:
			* Guiliani's main loop
			* Input event handling
			* Invalidating and redrawing
			* Streaming
			* Performance Optimization


	== GSE ==		== GSE ==

Sascha at 06:55, 21 June 2021

2021-06-21T06:55:24Z

← Older revision		Revision as of 06:55, 21 June 2021
Line 20:		Line 20:


	==== Q: GSE does not recognize my license and still has limitations ====		=== Q: GSE does not recognize my license and still has limitations ===
	'''A:''' If you have obtained a license you also want to use with the GSE, please place the license-file into the main-folder of the GSE where also the executable resides. Re-start the GSE. You can check the currently active limitations for your license in the about-dialog (Menu Help->About).		'''A:''' If you have obtained a license you also want to use with the GSE, please place the license-file into the main-folder of the GSE where also the executable resides. Re-start the GSE. You can check the currently active limitations for your license in the about-dialog (Menu Help->About).

	== ~~General~~ ==		=== Q: Can assets be stored in RGB565 format to preserve Flash memory? And what about transparency? ===
			'''A:''' Assets (images and fonts) can be exported from the GSE in various formats, each of it having advantages and disadvantages. Fonts can be left native and use the FreeType font-engine on the device or converted into ALPHA4/ALPHA8 bitmap-fonts to be used with the TES GlyphLib.
			Images can be exported - additionally to native which will require a fair amount of RAM for unpacking the image - in the formats RAW and RLE, which can be blitted directly from their storage (e.g. QSPI-flash) with only little (ca. 20 bytes) of RAM needed for managing the image in Guiliani. These two formats have different sub-formats like RAW565 or RAW4444 which can be used for saving memory or preserving transparency without having to use a 32-bit image.

			=== Q: Can images that are not available at compile-time be displayed during runtime ===
			'''A:''' Since the GSE-project is completely independent from your code and its compile-time (the only link is a bunch of header-files which are used for accessing objects and resource from your code) you can define a placeholder image which will be filled later during runtime or just use Guiliani's ability for dynamic resources, which provides methods to register specific files as resources during runtime. This offers the highest flexibility possible to suit your needs. (see Documentation of CGUIResouceManager)
			The only situation where the GSE-project is indeed coupled to your compile-time is when exporting the GSE-project as a header-file to be placed alongside with the application-code inside the ROM-section. But normally the best approach is to export the project as a Resource-file which gets loaded to any section you want. This also provides the possibility to update or exchange the whole project and keeping the application-binary the same (e.g. for having several different layouts or skins, but providing the same functionality - of course). Or to update the application-binary when there is a software-update.

			=== Q: Does the GSE support versioning ===
			'''A:''' The GSE-project and its files are in the XML-format and human-readable or even versionable. You can push the contents into a svn- or git-repository like any other file (including the assets of course) to be able to pull out any version at a specific moment in time. The GSE does not provide this kind of integration, thus it must by done by hand or a tool (including adding or removing files). A Merge should - by the text-nature of the files - be also possible, but having the same risk as it has on normal source-files when having conflicts. These need to be resolved by hand which can get tricky as it is for source-code to keep the integrity of the GSE-project. Please note: when having translations in languages which are using UTF-8 encoding your versioning system has to support this to prevent loss of information.

			== Guiliani ==

			=== Q: How is memory allocation done in Guiliani ===
			'''A:''' Guiliani allocates and de-allocates (both MemLeak-tested) all memory needed for its objects, including the objects which are part of the GUI-tree when it is needed. If an object is deleted, e.g. because its parent or itself is removed from the GUI-tree, all the allocated memory gets freed. Guiliani uses
			the functions provided by the operating system or BSP for allocation. This - since Guiliani is a C++-only GUI-framework - includes the C++-specific operators new, new[] and delete, delete[] (maybe a custom-mapping if needed).
			Memory which is not managed by Guiliani is of course not covered by this technique. If an user-created object will be taken over by Guiliani, Guiliani will also manage its lifecycle including memory-deallocation. If this is the case the behaviour will be described in the API-function-documentation.
			Guiliani provides some mechanisms like SmartPtr (including reference-count) to safely allocate memory which will automatically be deleted when not used anymore.
			You do not need to allocate any memory Guiliani will be using beforehand, this will be done by Guiliani itself. The memory for the framebuffer is a special case, since it might be placed in a different memory-region (e.g. SRAM). So the allocated pointers are just given to Guiliani during initialization.
			Regarding tracking pages which are displayed: Guiliani will manage the lifecycle of all object inside the GUI-tree (visible or not) and react to all user-actions like adding/removing/rearranging etc. accordingly. Objects are shown, when the user says they should be shown. I.e. when an object is added to the GUI-tree during runtime, Guiliani will show or hide it, according to its visible-state in the next Redraw-cycle.

			=== Q: Are primitive drawing operations supported? ===
			'''A:''' For manually drawing graphic primitives on the screen, there a many methods included in the Graphics-Wrapper Guiliani is using. This wrapper abstracts from the underlying Graphics-API (OpenGL, eGML or D/AVE) and provides a generic interface to use these operations. This includes for version 2.4 of Guiliani lines, rectangles, ellipses, arcs, rings, image-blits (stretch and rotation if supported) and texts. Please see the documentation for GfxWrap in our online documentation. These methods are a kind of low-level compared to the high-level widgets Guiliani provides for drawing primitives (CGUIGeometryObject) and texts (CGUITextField), but you will use these when creating an application-specific widget which should draw a line inside an ellipse and beneath a text.

	=== Q: What is a Custom Extension ===		=== Q: What is a Custom Extension ===
	'''A:''' A Custom Extension is a possibility to enhance the GSE with a custom-made piece of functionality. this could be a layouter, behaviour, command or widget. the advantage when using Custom Extensions is that the designer can use them directly within the GSE and play around with them without any programming knowledge. the programmer just fills the important parts of the generated shell with custom code for visual representation and behaviour.<br/>		'''A:''' A Custom Extension is a possibility to enhance the GSE with a custom-made piece of functionality. this could be a layouter, behaviour, command or widget. the advantage when using Custom Extensions is that the designer can use them directly within the GSE and play around with them without any programming knowledge. the programmer just fills the important parts of the generated shell with custom code for visual representation and behaviour.<br/>
	'''The license limits for Custom Extensions only apply to the usability within the GSE. Guiliani can, of course, be extended with new customized functionality with no restrictions.'''		'''The license limits for Custom Extensions only apply to the usability within the GSE. Guiliani can, of course, be extended with new customized functionality with no restrictions.'''


	=== Q: Run Guiliani on Baremetal ===		=== Q: Run Guiliani on Baremetal ===
Line 41:		Line 61:
	The port can be part of a license contract or it is possible to buy a source code license which will enable you to port on your own.		The port can be part of a license contract or it is possible to buy a source code license which will enable you to port on your own.
	For licensing information and pricing please contact our sales.		For licensing information and pricing please contact our sales.


	=== Q: Sample Guiliani-Application ===		=== Q: Sample Guiliani-Application ===
Line 191:		Line 210:
	</syntaxhighlight>		</syntaxhighlight>

			=== Q: How are errors indicated from the business-logic handled? E.g. during a transition? ===
			'''A:''' Since Guiliani treats the GUI totally transparent, it can't determine any error-state or whatever application-specific things you have. But, when an error is encountered in your business-logic you can of course react to this. E.g. by setting an error-state which gets sent to the GUI-code which executes a command including specific behaviour (e.g. showing a popup or changing to a defined error-page). You can interact with the GUI and tell it what to do in such a case. Please note that execution here is not immediatety, instead the command will be inserted into a queue and Guiliani will execute it in the next loop-iteration to assure thread-safety inside the GUI-context.

	=== Q: Graphic controller that supports only 4 bits per pixel ===		=== Q: Graphic controller that supports only 4 bits per pixel ===

Sascha at 06:43, 21 June 2021

2021-06-21T06:43:00Z

Administrator at 17:14, 4 January 2021

2021-01-04T17:14:41Z

← Older revision		Revision as of 17:14, 4 January 2021
Line 1:		Line 1:
	=== GSE ===		<metadesc>Frequently asked questions about the embedded GUI framework Guiliani.</metadesc>
			== GSE ==


	==== Q: GSE is not starting ====		=== Q: GSE is not starting ===
	'''A:''' if the GSE is not starting, please check the GSE.log-file for errors which prevent the GSE from opening. This file is located in the same folder as the GSE-binary.		'''A:''' if the GSE is not starting, please check the GSE.log-file for errors which prevent the GSE from opening. This file is located in the same folder as the GSE-binary.

Line 11:		Line 12:


	==== Q: menu in GSE not completely visible on Windows ====		=== Q: menu in GSE not completely visible on Windows ===
	'''A:''' if the menu-bar in GSE is not completely visible, but somewhat shifted upwards, there might be a problem with the driver of the graphics card. GSE uses by default OpenGL for display and there are known issues when using Intel graphic cards, especially on Laptops. As a solution we recommend updating the drivers of the graphics card.		'''A:''' if the menu-bar in GSE is not completely visible, but somewhat shifted upwards, there might be a problem with the driver of the graphics card. GSE uses by default OpenGL for display and there are known issues when using Intel graphic cards, especially on Laptops. As a solution we recommend updating the drivers of the graphics card.


	==== Q: GSE sometimes does not exit properly on Linux ====		=== Q: GSE sometimes does not exit properly on Linux ===
	'''A:''' This could happen on various Linux-Versions, especially when using VirtualBox or VMWare. Possibly your sound-card has crashed. You can deactivate the sound-card and/or update to the latest version of virtualizing software/operating system and try again.		'''A:''' This could happen on various Linux-Versions, especially when using VirtualBox or VMWare. Possibly your sound-card has crashed. You can deactivate the sound-card and/or update to the latest version of virtualizing software/operating system and try again.

Administrator at 12:54, 17 December 2020

2020-12-17T12:54:47Z

← Older revision		Revision as of 12:54, 17 December 2020
Line 251:		Line 251:
	Feedback would help us to decide which IDE might be the best.		Feedback would help us to decide which IDE might be the best.

	'''A:''' the most versatile solution might be using Eclipse with GCC, since this covers a variety of use-cases. If certification is ~~neccessary~~ IAR will be the best choice.		'''A:''' the most versatile solution might be using Eclipse with GCC, since this covers a variety of use-cases. If certification is necessary IAR will be the best choice.

	==== Q: How is a "Swipe" handled in Guiliani ====		==== Q: How is a "Swipe" handled in Guiliani ====

Sascha at 07:37, 14 October 2020

2020-10-14T07:37:35Z

← Older revision		Revision as of 07:37, 14 October 2020
Line 253:		Line 253:
	'''A:''' the most versatile solution might be using Eclipse with GCC, since this covers a variety of use-cases. If certification is neccessary IAR will be the best choice.		'''A:''' the most versatile solution might be using Eclipse with GCC, since this covers a variety of use-cases. If certification is neccessary IAR will be the best choice.

			==== Q: How is a "Swipe" handled in Guiliani ====

			'''A:''' Guiliani uses the term "Drag" instead of "Swipe". You will generally use DoDrag- and DoDragEnd-events in your control.

			the event-sequence you will get in your control will be the following during a drag:
			* DoButtonDown with the current position on the screen
			* several DoDrag with the new position on the screen and a delta for both axes
			* DoDragEnd when lifting the finger with the final position

			with the help of these events you can react on almost every movement of the finger,
			even a circular movement would be possible.

			here is a short sample-implementation for demonstration:

			<syntaxhighlight>
			eC_Bool XXX::DoButtonDown(const eC_Value &vAbsX, const eC_Value &vAbsY)
			{
			// Store the data for dragging.
			m_kDragStart = CGUIPoint(vAbsX, vAbsY);
			m_uiDragStarted = GETTIMER.GetTime();

			return true;
			}

			eC_Bool XXX::DoDrag(const eC_Value &vDeltaX, const eC_Value &vDeltaY, const eC_Value &vAbsX, const eC_Value &vAbsY)
			{
			if (
			((m_eDirection == CGUICommonEnums::OR_HORIZONTAL) && (abs(m_kDragStart.m_vX - vAbsX) >= m_vMinimumDragDistance)) \|\|
			((m_eDirection == CGUICommonEnums::OR_VERTICAL) && (abs(m_kDragStart.m_vY - vAbsY) >= m_vMinimumDragDistance))
			)
			{
			// We support only scrolling into the specified direction (via object attribute).
			eC_Value vDragDelta = eC_FromInt(0);
			eC_Value vDragAbs = eC_FromInt(0);

			if (m_eDirection == CGUICommonEnums::OR_HORIZONTAL)
			{
			vDragDelta = vDeltaX;
			vDragAbs = vAbsX - m_kDragStart.m_vX;
			}
			else if (m_eDirection == CGUICommonEnums::OR_VERTICAL)
			{
			vDragDelta = vDeltaY;
			vDragAbs = vAbsY - m_kDragStart.m_vY;
			}
			// adjust position of container

			return true;
			}
			return false;
			}

			eC_Bool XXX::DoDragEnd(const eC_Value &vAbsX, const eC_Value &vAbsY)
			{
			// drag has ended, use the distance to the starting-point for the direction

			return true;
			}
			</syntaxhighlight>

			# in the DoButtonDown-method the starting-position is saved to use it for the detection of the overall direction. of course you can only use the delta-values for x and y in DoDrag, but this is only the difference between the last event and the current one. when you want to calculate the direction at the end in DoDragEnd you will need the start of the event-sequence.
			# in the DoDrag-method we use the direction-attribute (m_eDirection) of the control and the difference of the position at the beginning of the event-sequence and the current position to see if the movement should result in an reaction of the control. we use a threshold so the processing will be done only if the drag is further away from the starting-position than the threshold. this provides a smoother feedback. if so we use the variables vDelta and vDragAbs for further processing, e.g. move the content of the control to the specifed position during the drag.
			# in DoDragEnd the event-sequence has reached its end and the final processing will be done, e.g. go to the next or the previous page based on the distance between the starting point (DoButtonDown) and the current position.

			<b>please note that the delta-values for DoDrag are always in screen-orientation, thus
			the y increases towards the bottom. this is different from the mathematical sense.</b>

	=== Renesas ===		=== Renesas ===

Sascha: /* GSE */

2019-04-09T10:20:54Z

GSE

← Older revision		Revision as of 10:20, 9 April 2019
Line 17:		Line 17:
	==== Q: GSE sometimes does not exit properly on Linux ====		==== Q: GSE sometimes does not exit properly on Linux ====
	'''A:''' This could happen on various Linux-Versions, especially when using VirtualBox or VMWare. Possibly your sound-card has crashed. You can deactivate the sound-card and/or update to the latest version of virtualizing software/operating system and try again.		'''A:''' This could happen on various Linux-Versions, especially when using VirtualBox or VMWare. Possibly your sound-card has crashed. You can deactivate the sound-card and/or update to the latest version of virtualizing software/operating system and try again.


	==== Q: GSE does not recognize my license and still has limitations ====		==== Q: GSE does not recognize my license and still has limitations ====

Sascha: /* GSE */

2019-04-09T10:20:36Z

GSE

← Older revision		Revision as of 10:20, 9 April 2019
Line 18:		Line 18:
	'''A:''' This could happen on various Linux-Versions, especially when using VirtualBox or VMWare. Possibly your sound-card has crashed. You can deactivate the sound-card and/or update to the latest version of virtualizing software/operating system and try again.		'''A:''' This could happen on various Linux-Versions, especially when using VirtualBox or VMWare. Possibly your sound-card has crashed. You can deactivate the sound-card and/or update to the latest version of virtualizing software/operating system and try again.

			==== Q: GSE does not recognize my license and still has limitations ====
			'''A:''' If you have obtained a license you also want to use with the GSE, please place the license-file into the main-folder of the GSE where also the executable resides. Re-start the GSE. You can check the currently active limitations for your license in the about-dialog (Menu Help->About).

	=== General ===		=== General ===

← Older revision		Revision as of 06:43, 21 June 2021
Line 23:		Line 23:
	'''A:''' If you have obtained a license you also want to use with the GSE, please place the license-file into the main-folder of the GSE where also the executable resides. Re-start the GSE. You can check the currently active limitations for your license in the about-dialog (Menu Help->About).		'''A:''' If you have obtained a license you also want to use with the GSE, please place the license-file into the main-folder of the GSE where also the executable resides. Re-start the GSE. You can check the currently active limitations for your license in the about-dialog (Menu Help->About).

	=== General ===		== General ==


	==== Q: What is a Custom Extension ====		=== Q: What is a Custom Extension ===
	'''A:''' A Custom Extension is a possibility to enhance the GSE with a custom-made piece of functionality. this could be a layouter, behaviour, command or widget. the advantage when using Custom Extensions is that the designer can use them directly within the GSE and play around with them without any programming knowledge. the programmer just fills the important parts of the generated shell with custom code for visual representation and behaviour.<br/>		'''A:''' A Custom Extension is a possibility to enhance the GSE with a custom-made piece of functionality. this could be a layouter, behaviour, command or widget. the advantage when using Custom Extensions is that the designer can use them directly within the GSE and play around with them without any programming knowledge. the programmer just fills the important parts of the generated shell with custom code for visual representation and behaviour.<br/>
	'''The license limits for Custom Extensions only apply to the usability within the GSE. Guiliani can, of course, be extended with new customized functionality with no restrictions.'''		'''The license limits for Custom Extensions only apply to the usability within the GSE. Guiliani can, of course, be extended with new customized functionality with no restrictions.'''


	==== Q: Run Guiliani on Baremetal ====		=== Q: Run Guiliani on Baremetal ===
	Could you help us on how to start running a Guiliani application on a system without RTOS?		Could you help us on how to start running a Guiliani application on a system without RTOS?

Line 43:		Line 43:


	==== Q: Sample Guiliani-Application ====		=== Q: Sample Guiliani-Application ===
	We got the Guiliani evaluation kit and we are able to install it and use it. We feel that the flow of the existing tutorial application is very difficult to understand.		We got the Guiliani evaluation kit and we are able to install it and use it. We feel that the flow of the existing tutorial application is very difficult to understand.
	# Can you provide us a sample GUI application like a screen with controls on it?		# Can you provide us a sample GUI application like a screen with controls on it?
Line 89:		Line 89:


	==== Q: How do I achieve rounded corners for rectangles ====		=== Q: How do I achieve rounded corners for rectangles ===
	I am trying to create a custom icon button. I am trying to achieve the following:		I am trying to create a custom icon button. I am trying to achieve the following:
	# Rounded corners		# Rounded corners
Line 192:		Line 192:


	==== Q: Graphic controller that supports only 4 bits per pixel ====		=== Q: Graphic controller that supports only 4 bits per pixel ===
	Our software will have to interface with a touchscreen via a graphic controller that supports only 4 bits per pixel and 8 bpp. Could there be any issue for Guiliani to support 8 bpp or 4 bpp?		Our software will have to interface with a touchscreen via a graphic controller that supports only 4 bits per pixel and 8 bpp. Could there be any issue for Guiliani to support 8 bpp or 4 bpp?

Line 204:		Line 204:


	==== Q: CGLImage linker issue ====		=== Q: CGLImage linker issue ===
	I was trying to use CGLImage for drawing an icon, but it seems that I couldn’t link the code as the definition for CGLImage constructor is missing. Can you please tell me where I can find the definition, in which library file is the definition included.		I was trying to use CGLImage for drawing an icon, but it seems that I couldn’t link the code as the definition for CGLImage constructor is missing. Can you please tell me where I can find the definition, in which library file is the definition included.

Line 210:		Line 210:


	==== Q: Transitions ====		=== Q: Transitions ===
	I need some help in screen transition. The problem is briefed below.		I need some help in screen transition. The problem is briefed below.
	# I have a ScreenContainer derived from CGUI which gets added to Screen		# I have a ScreenContainer derived from CGUI which gets added to Screen
Line 232:		Line 232:


	==== Q: Pixel Processing ====		=== Q: Pixel Processing ===
	Does Guiliani Supports Pixel Processing?		Does Guiliani Supports Pixel Processing?

Line 240:		Line 240:


	==== Q: Is the STM32F429 supported ====		=== Q: Is the STM32F429 supported ===
	There is a nice cheap development board including display available from ST called STM32F429 Discovery.		There is a nice cheap development board including display available from ST called STM32F429 Discovery.
	Is it possible to use Guiliani to develop HMIs?		Is it possible to use Guiliani to develop HMIs?
Line 254:		Line 254:
	'''A:''' the most versatile solution might be using Eclipse with GCC, since this covers a variety of use-cases. If certification is necessary IAR will be the best choice.		'''A:''' the most versatile solution might be using Eclipse with GCC, since this covers a variety of use-cases. If certification is necessary IAR will be the best choice.

	==== Q: How is a "Swipe" handled in Guiliani ====		=== Q: How is a "Swipe" handled in Guiliani ===

	'''A:''' Guiliani uses the term "Drag" instead of "Swipe". You will generally use DoDrag- and DoDragEnd-events in your control.		'''A:''' Guiliani uses the term "Drag" instead of "Swipe". You will generally use DoDrag- and DoDragEnd-events in your control.
Line 321:		Line 321:
	the y increases towards the bottom. this is different from the mathematical sense.</b>		the y increases towards the bottom. this is different from the mathematical sense.</b>

	=== Renesas ===		== Renesas ==

	==== Q: What is the procedure for porting your product to custom hardware? ====		=== Q: What is the procedure for porting your product to custom hardware? ===
	# Port the QSPI Loader. You will find the needed information in the doc folder of the RZ_A1H_QSPI_LOADER project. The main topics there are the used FLASH device and its port configuration.		# Port the QSPI Loader. You will find the needed information in the doc folder of the RZ_A1H_QSPI_LOADER project. The main topics there are the used FLASH device and its port configuration.
	# You can change the Display size by changing FRAME_BUFFER_WIDTH and FRAME_BUFFER_HEIGHT in Macro defines section of the compiler configuration of the application (Demo: SR_GuilianiDemo). The number of Frame_Buffers can be defined with the CreateInstance-Call of the GfxWrapeGML in StreamRunimeStartup_FreeRTOS.cpp.		# You can change the Display size by changing FRAME_BUFFER_WIDTH and FRAME_BUFFER_HEIGHT in Macro defines section of the compiler configuration of the application (Demo: SR_GuilianiDemo). The number of Frame_Buffers can be defined with the CreateInstance-Call of the GfxWrapeGML in StreamRunimeStartup_FreeRTOS.cpp.
Line 331:		Line 331:


	==== Q: How can I change color depth? ====		=== Q: How can I change color depth? ===
	The project is set to 16bpp. To enable 32bpp you can undefine FRAME_BUFFER_BITS_PER_PIXEL_16 and replace the initialization of the graphics wrapper in StreamRunimeStartup_FreeRTOS.cpp with CGfxWrapeGML::CreateInstance(FRAME_BUFFER_WIDTH, FRAME_BUFFER_HEIGHT, eGML::BM_RGB32);		The project is set to 16bpp. To enable 32bpp you can undefine FRAME_BUFFER_BITS_PER_PIXEL_16 and replace the initialization of the graphics wrapper in StreamRunimeStartup_FreeRTOS.cpp with CGfxWrapeGML::CreateInstance(FRAME_BUFFER_WIDTH, FRAME_BUFFER_HEIGHT, eGML::BM_RGB32);


	==== Q: Ram start address in linker script for Renesas RZ/A ====		=== Q: Ram start address in linker script for Renesas RZ/A ===
	I've started to look into Guiliani 2.0 SDK for RZ/A and I noticed maybe some bug in linker script RZA1H_GCC_RAM_APP.ld		I've started to look into Guiliani 2.0 SDK for RZ/A and I noticed maybe some bug in linker script RZA1H_GCC_RAM_APP.ld
	for SR_ShowRoom project. It is: RAM_START = 0x20024000;		for SR_ShowRoom project. It is: RAM_START = 0x20024000;
Line 367:		Line 367:


	==== Q: <new> and bad_alloc() warnings after compiling ====		=== Q: <new> and bad_alloc() warnings after compiling ===
	SR_ShowRoom is compiling without errors and I can start debugging		SR_ShowRoom is compiling without errors and I can start debugging
	but I have warnings "unresolve inclusion: <new" and "function bad_alloc() could not be resolved" in StreamRuntime_FreeRTOS.cpp after compiling.		but I have warnings "unresolve inclusion: <new" and "function bad_alloc() could not be resolved" in StreamRuntime_FreeRTOS.cpp after compiling.
Line 384:		Line 384:


	==== Q: To run in RAM ====		=== Q: To run in RAM ===
	We are developing an application with RZ and Guiliani.		We are developing an application with RZ and Guiliani.
	Our PCB is very similar to the Renesas Demo Board.		Our PCB is very similar to the Renesas Demo Board.