Is it possible that something in your code is setting the value back to its original? I am unable to reproduce this (try, for example, the Parameters example project)
i tried the parameter project….there it works sometimes, sometime not. I could also change the boolean state by touching in the main display close to the parameter boolean! I really think there is something that has changed for the worse here.
In the Parameters project touching the screen does toggle the boolean parameter (it’s intentional). But it should also work by tapping in the sidebar, I’ll keep trying to reproduce too. iPad?
i wrote a test project with one line of code to define a parameter.boolean. I see the same thing, sometimes it will toggle, many times it returns back to the original state.
Could you make it remember the state of the parameter panel when you tap it?
If you tap it while the parameter panel is showing, it will switch to full screen mode, but if you tap it again it will just expand the bottom buttons, it won’t go back to having the parameter panel open.
@sim - thanks for the update, still working on the changes. Noted, with the new buttons in the parameter window, would it be possible to have an option there where the dual arrow button defaults to being present in the corner of the fullscreen, no parameter window with the button for open close parameter window is present in the bottom corner ?
Funnily enough I was going to suggest something along those lines. What I envisaged was a button, as I described above, which is present in any of the 4 corners (programmable moving the button into non-critical area of the screen ie where the programmer has not used the area for critical output). On touching the button a separate window can then be opened with all the relevant options we are used to - maybe even in centre screen. Note the window button widow having good contrast to show buttons up without background issues.
On pressing the capture screen button the button window closes before the screen capture).
I even wondered if it was worth making the button window programmable
Codes.options = true/false
Which you could put in the Codea templates by default.
@sim my apologies for above comment, your mods do seem to operate as I described if there are no errors, several of my tests had errors present.
However this one didn’t
function setup()
--
sW, sH, cW, sH = WIDTH, HEIGHT, WIDTH//2, HEIGHT//2
south, north = HEIGHT*0.32, HEIGHT*0.72
side = 400
strokeWidth(8)
end
function draw()
-- This sets a dark background color
background(40, 40, 50)
rectMode(CENTER)
fill(80, 173, 233)
stroke(255, 14, 0)
strokeWidth(50)
rect(cW,north,side,side)
fill(150, 233, 80)
strokeWidth(80)
rect(cW, south, side, side)
end
