Main Area and Open Discussion > Living Room
It's alive, it's alive!!! mwahaha! - WinButtons and 7" touchscreen works
Ath:
The new cursor memory feature doesn't seem to make any difference regardless of the setting it's on
-nudone (September 07, 2011, 08:03 AM)
--- End quote ---
Setting the CursorRestore buffer to Small should give the same buffersize as the previous version, but I also tweaked the buffer-fill-code to try to be a bit more efficient. Might be I messed up something :-[
There is also a strange layout problem.
-nudone (September 07, 2011, 08:03 AM)
--- End quote ---
Could you PM or e-mail me that layout file, so I can have a look at it?
I have noticed that, even though I firmly press the keys to compile the AutoIt3 source, it sometimes produces a bad/partly corrupted .exe, so I should probably do some more quality assurance before packing stuff into the zip-file. :huh:
I'll re-compile later today, and upload again (can't ftp from work).
One, thought and question: are the old .wbuc button templates compatible with the updates of WinButtonsEdit?
It's going to be a long process of having to recreate all the templates everytime if so.
-nudone (September 07, 2011, 08:10 AM)
--- End quote ---
The file-format has been backward compatible from day one, I only added settings (and sections) that are not interpreted by older versions of WinButtons but they do no harm. And ofcourse the default extension changed from .ini to .wbuc, some time ago, but it does work with .ini files equally well.
When unpacking my zip-file, just get the *.exe and *.readme.txt files. Unzip *.au3 if you want the source, all other files are hardly ever changed and meant as examples for new users.
For the keyboard shortcut keys I'm working on built-in support for WB, to avoid the load-time of WinSendKeys, and the AutoIt3 'rules' can be found here. Anything you can Send(), you can use with WB (though WinSendKeys can do a bit more, like mouse-clicks).
The WB built-in Send function will get a new command (not '-send'), so that would require a 1-time change to your .wbuc file(s). :-\
nudone:
Okay, sounds good.
I think I'll create a new basic set of buttons to test things with until you've had chance to test everything out yourself with the touchscreen.
I'll email you the template I've been using until now.
nudone:
I'm now using the previous version of WinButtonEdit (when "Restore cursor after button" was first included to it) and have just created a 4 x 3 button template.
All seemed find but on reopening the template inside WBE the "Photoshop" group I've created has lost all the button labels - and, the background has change to red for this group only.
As this is the first task I've done since extracting this version of WinButtons (today) it appears that the fault has been there all along. I'm going to proceed and put all the labels in again and hopefully they stick. I'll report back what happens...
edit:
I forgot to mention the odd bit about this: when running the related .wbuc as a live set of buttons, they labels appear, plus the background color is black, so all appears correct. So, somehow WBE isn't reading the contents of the .wbuc file when it is edited.
another edit:
I better just clarify what I said "labels" but in WBE these are the "Captions".
nudone:
Okay, maybe I'm just not understanding what each feature is in the editor. What is the "Caption" for? I've renamed the buttons just using their "Name" - which makes sense and I probably should have not used "Captions" anyway.
The background color of the group appears to be working correctly now too. I've placed "#" inside {} which is being used with one of the hotkey commands, which now makes the button work correctly - but I wonder if this was, perhaps, making the editor go funny with the background color. I see that # is intepreted as Winkey by AutoIt unless it is used like {#} so I'm guess this could have been the problem.
Ath:
A point of attention:
If WinButtons or WinButtonEdit have a current file that is not named WinButtons.wbuc or WinButtons.ini, they try to read any missing Settings values from WinButtons.wbuc or .ini (dependent on/same as the extension of the current file).
So if you have said file in the current directory while editing, but not in the actual directory where WinButtons is reading the current file, behavior will be different. (there is a corresponding remark in the WinButtons.readme.txt file about this)
And a small tip: WBE offers to run the current file with WinButtons from the 'File/Run WinButtons with current file Ctrl-R' menuitem, for a quick 'Real World' test :)
The cause for losing all Captions is not clear to me, I've never seen that happen before :'(, I'll investigate.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version