aliazzz modified a comment on ticket #74

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).

aliazzz modified a comment on ticket #74

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).

aliazzz posted a comment on ticket #74

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?

aliazzz created ticket #74

clicking upper left cforge logo

aliazzz created ticket #73

CfUnit API Reference keeps showing up as 'revised'

aliazzz created ticket #9

Error: The file 'formatinfo' is missing in the repository for visual elements

aliazzz committed [r54]

aliazzz committed [r53]

aliazzz committed [r52]

FB_StringBuffer renamed to FB_StreamBuffer

aliazzz committed [r51]

small fix

aliazzz created ticket #72

python scripting examples mssing because of licensing

aliazzz modified a wiki page

Project Overview

aliazzz modified a wiki page

Project Overview

aliazzz committed [r50]

Ingo was right, there was a t missing!

aliazzz committed [r49]

atomic project v0.3.2.0

aliazzz committed [r48]

comments

aliazzz modified a wiki page

Home

aliazzz committed [r47]

drone.yml

aliazzz modified a wiki page

Home

aliazzz committed [r45]

root of the svn library

aliazzz committed [r44]

root of the svn library

aliazzz committed [r46]

update of

aliazzz committed [r43]

temporary move of files to enable project commit

aliazzz modified a wiki page

Home

aliazzz committed [r42]

aliazzz committed [r41]

V0.3.2.0

aliazzz modified a wiki page

Home

aliazzz modified a comment on a wiki page

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

aliazzz modified a comment on a wiki page

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

aliazzz modified a comment on a wiki page

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

aliazzz posted a comment on a wiki page

No, You should declare a BYTE byBitfield : BYTE; Then you can address each bit as follows; byBitfield.0 := xMyBool0; .. byBitfield.7 := xMyBool7; Good luck

aliazzz committed [r40]

v0.3.1.0