Activity for aliazzz
-
aliazzz committed [r292]
-
-
Currently a pre-alpha results.xml is generated.
-
This said, when the logo is pressed from the app the dissapearing and reappearing menu makes sense. However, it doesn't make sense to me in a full blown browser. IMHO I don't mind the side menu at all, it even better if it's always there, available to me. So, can you differentiate the click-event from the browser agent/platform? E.g. If the button is pressed from the app, something else happens then if the button is pressed from a real webbrowser (non mobile platform).
-
This said, when the logo is pressed from the app the dissapearing and reappearing menu makes sense. However, it doesn't make sense in a full blown browser! So, can you differentiate the click-event from the browser agent/platform? E.g. If the button is pressed from the app, something else happens then if the button is pressed from a real webbrowser (non mobile platform).
-
This said, when the logo is pressed from within on a smaller screen (less real-estate) the appearing/dissapearing menu makes sens. However, it doesn't make sense in a full blown browser! Can you differentiate the click-event from the browser agent/platform?
-
clicking upper left cforge logo
-
CfUnit API Reference keeps showing up as 'revised'
-
Error: The file 'formatinfo' is missing in the repository for visual elements
-
-
-
-
standalone XmlResultFormatter project
-
standalone XmlResultFormatter project
-
XmlFormatter Branche
-
-
Branch of CfUnit for debugging purpose
-
-
-
FB_StringBuffer renamed to FB_StreamBuffer
-
small fix
-
python scripting examples mssing because of licensing
-
-
footer
-
Project Overview
-
Project Overview
-
Ingo was right, there was a t missing!
-
atomic project v0.3.2.0
-
comments
-
Home
-
drone.yml
-
Home
-
root of the svn library
-
root of the svn library
-
update of
-
temporary move of files to enable project commit
-
Home
-
Library shrunk from 220MB to 470Kb
-
-
V0.3.2.0
-
binary update of library and project
-
FB_XmlFileFormatter: TODO Debug/build xmlfile further
-
v1.1.0.1
-
binary update of library and project
-
v1.1.0.1
-
v1.1.0.1 Modified CfUnitRunner to accomodate for the new introduced XmlFileFormatter
-
CfUnit Verifier for v1.1.0.1
-
Library/CfUnit.library v1.1.0.1
-
added code repo url
-
added code repo url
-
added code repo url
-
Trunk updated to v1.1.0.1
-
Trunk update v1.0.0.1
-
updated/added;
-
Home
-
No, You should declare a BYTE in the PLC Code byBitfield : BYTE; Then you can address each bit as follows; byBitfield.0 := xMyBool0; .. byBitfield.7 := xMyBool7; Try to avoid own DUT's (enums, structs) in the Devdesc.xml and stick to basic primitives like BYTE, DINT, REAL, WORD etc. This will make your life easier in editing the devdesc.xml. Offcourse if you want to use them, no problem, but you have to declare them in your code AND the devdes.xml file, so in two seperate places! Good luck
-
No, You should declare a BYTE in the PLC Code byBitfield : BYTE; Then you can address each bit as follows; byBitfield.0 := xMyBool0; .. byBitfield.7 := xMyBool7; Try to avoid own DUT's (enums, structs) and stick to basic primitives like BYTE, DINT, REAL, WORD etc. This will make your life easier. Good luck
-
No, You should declare a BYTE in the PLC Code byBitfield : BYTE; Then you can address each bit as follows; byBitfield.0 := xMyBool0; .. byBitfield.7 := xMyBool7; Try to avoid own DUT's (enums, structs) and stick to basic primitives like BYTE, DINT, REAL, WORD etc. Good luck
-
No, You should declare a BYTE byBitfield : BYTE; Then you can address each bit as follows; byBitfield.0 := xMyBool0; .. byBitfield.7 := xMyBool7; Good luck
-
-
https://forge.codesys.com/prj/cfunit/home/Tutorial/
-
various small text tweaks
-
small updates
-
v0.3.1.0