Software Forum Discussions

I do like the way these graphic editors look, but I don't think they are so easy to handle when it comes to zooming and panning throughout the pages - though they aren't really big.

As I am an Altium Designer user, I think it'd be quite handy to go about their solution, which is:

Zoom in : Ctrl + mouse wheel forward / keystroke(configurable)

Zoom out : Ctrl + mouse wheel backward / keystroke(configurable)

Pan left: Shift + mouse wheel forward / left arrow key (configurable) / 2D mouse wheel left

Pan right: Shift + mouse wheel backward / right arrow key (configurable) / 2D mouse wheel right

Pan up: mouse wheel forward / up arrow key (configurable)

Pan down: mouse wheel backward / down arrow key (configurable)

Dragging: Hold right button on the mouse and move the cursor.

With the help of mice equiped with configurable buttons, many people (including me) are getting used to navigating graphic GUI with only one hand. It'd make us a lot more efficient if such enhancement was introuduced. Thanks.

I am using PSoC 3 Creator 1, and PSoC 1 Designer 5. I noted that Designer has no way to set tab settings in the IDE, nor does it have any way to control the cursor blink rate, (I want to set the blink rate to off). It does not follow the standard windows system settings. I see Creator 1 also has the same problem. Is there any way to change both the blink rate on both development tools, and the tab setting on Designer?

When I read the datasheet of I2C(I2CHW in PSoC Creator), I found when we use Slave mode, the function "uint8 I2C_SlaveStatus(void)" will be used to check the status for I2C Slave, and also, we can see the example code in the datasheet as below:

uint8 wrBuf[10];
uint8 userArray[10];
uint8 byteCnt;
I2C_SlaveInitWriteBuf((uint8 *) wrBuf, 10);
/* Wait for I2C master to complete a write */
for(;1 /* loop forever */
{
/* Wait for I2C master to complete a write */
if(I2C_SlaveStatus( ) & I2C_SSTAT_RD_CMPT )
{
byteCnt = I2C_SlaveGetWriteBufSize( );
I2C_SlaveClearReadStatus( );
For(i=0; I < byteCnt; i++)
{
userArray = wrBuf; /* Transfer data */
}
I2C_SlaveClearWriteBuf( );
}
}


Why we can use the I2C_SSTAT_RD_CMPT to indicate the I2C Master has complete a write?
And I don't know when the I2C_SSTAT_RD_CMPT will be set?(if the I2C_SSTAT_RD_CMPT is set when we finished read the buffer, and when the last byte is transmitted, we will also read the wrBuf[], but then, the content in the buffer is not written by the Master?)