Sorry, didn't realize the Google API wasn't free anymore. (Apparently Bing's is, but it may be inferior?) This is not a high priority thing for me at all, just thought it would be an interesting idea.philo wrote:translate
Sounds like a good idea, the api costs money so I wouldn't use that.
However the free website may work.
Thanks, temporarily switching the TV to primary worked; can't believe I didn't try that before!philo wrote:toggle full-screen
The current development version is working dual screen (images displayed on the primary monitor, text and buttons on the secondary). I should be able to add a setting to choose which screen to use.
In the short term Guideme uses the primary monitor, so you could switch your TV to be the primary monitor to get it to work full screen and then switch back when you finish.
Personally, I like the idea of keeping the entire application confined to one screen (as opposed to just the picture on one monitor and the text and buttons on the other), but I'm open to new ideas. Perhaps this could be an option? I just think moving my eyes back and forth and refocusing on each could be somewhat distracting and remove the user from the "moment." Also, I'd prefer to have the other monitor dedicated to something else. In my case, the two screens are not very close to each other.
Additionally, as Lestrian alluded to, the current fullscreen mode isn't "truly" fullscreen in my opinion. There is still black space above and below the picture as well as the menu bar at the top. I think ideally the picture would occupy as close to 100% of the vertical space as possible, much like TeaseMe does currently.
I think if the debug window was not widely advertised and was brought up with a "secret" hotkey combination like in TeaseMe, that would quell some of the worries about "cheating." For those of us that are "hardcore" users it is probably very important, but many others many not even know it exists. For me, like the others who posted above me, I use it for selectively changing pages (particularly helpful if a flash tease is published with errors), see page names, how many pages exist, what target pages there are, picture and sound filenames, and hidden and secret timer durations, to name a few. There are other elements to the TeaseMe version, but these are the main ones I use. In general it is nice (educational) to see how all the elements of the page come together to work the way it does. (Although this can also be done with the Offline Editor!philo wrote:Debug window
I didn't use the debug screen in tease me, which is the main reason I have not implemented anything like it for Guideme. If it is useful then I can have a look at implementing something.
It may be worth having a list of what people feel is missing on the debug side, is the teaseme debug window "perfect" or can it be improved or provided in a better way.
If I am going to write something it may be better to do exactly what people need rather than just replicating what teaseme does.
(I must admit I find it a challenge to not "cheat" when I do a tease if the debug option is there so didn't want to make it too easy
) I could even imagine a debug window that allowed basic edits to those elements on the fly... 
Overall, I think the existing TeaseMe debug window is near-perfect. There are some elements I don't look at normally, but for a debugging tool it does what it's supposed to do, which is show you why each page is doing what it's doing.
