Jump to content

ClearDark

Members
  • Posts

    400
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by ClearDark

  1. I will include a "reset" function in 1.3. With this you can define every control "default" position and hitting the "RESET" button that will be added to the Tabs box will flip all switches to their original start-up positions. Synchronizing switches by using exported data is possible but limited. I will explore these features and see regarding future implementation in HT!
  2. Be sure to extract all the content. Including images. If HawgTouch can't find or can't access the images in the profile it will throw the error you received. If you extracted all the contents and still get the message it has to be file permission problems. If all the fails let me know and we'll help ya figure it out! On a side note, some of the new features that will be included in 1.3: - NEW! Rotary knobs with programmable positions - Switches now support a default starting position - Data export from A-10C! New "Network" controls that can parse information from the simulator. The A-10C warning lights panel will be the module which will be released for the next version demonstrating the new feature I have been digging alot into DCS lua the past few days. I've also found an alternative method to send keystrokes to the simulator. A method which doesn't require any keybindings. Its based creating a listener in DCS export file and sending commands to specific "devices". I will most likely incorporate this ability at a later stage.
  3. I suggest you use MadTommy's excellent profiles for both MFCD's and his marvelous UFC module. Both can be found here: http://forums.eagle.ru/showthread.php?t=70364 If you want help converting plates to HawgTouch tabs just shoot me a PM and I'll help you sort it out. I'm aware that HawgTouch profile making is very little documented and I intend to write a quick getting started manual prior to starting on the actual profile editor software. So I'm offering any help to anyone who wants to create something but lack the knowledge of howto :)
  4. HawgTouch doesn't support PDF's. HT main goal is to consume the least amount of memory from your system so you won't feel it running and it will not have any performance hit on your game. TouchBuddy supports PDF's, Movies and ActiveX controls, all which "clutter" up my system during actually playing the game. If you want checklists in HawgTouch, its relatively simple. Make a screenshot of the procedures you want to make, or make a nice large image with all the checklists you find necessary and just create a tab in HawgTouch with panel image as the one you just created. Name it accordingly and once you load the profile you can easily access the checklists. You can add as many as you want in any size you'd like. HawgTouch can scale your controls up or down so you can fit them all in one tab. I will take a look into PDF support and see the performance impact. If its not that large I will include a PDF support in the next version.
  5. Tommy! Your UFC is simply amazing! I will be using that one from now on! Thanks a bunch! Rep inbound!
  6. For letter keys, use lower-case. That works for me :) Don't use capital A's or Z's..just the regular lowercase letter. Let me know how it worked out!
  7. 1.25 is out. A big bug-squishing release! Check out the main post!
  8. The issue with "scaled" transparent panels is caused by the interpolation mode in C#. When resizing the image, the clear value of 255,0,255 is "smeared" at the edges resulting in a little fuchsia being displayed. I'm looking into that issue. Will probably be resolved in the next release! BTW Tommy I'm waiting eagerly for your UFC panel! :D
  9. Make sure you save the XML file and re-load the profile. Currently there is a bug with rocker switches, 2 state switches and 3 state switches. As stated earlier I will be releasing a new version very soon with these fixes and some more additions.
  10. Thanks for reporting this issue. I dove in the code and saw the problem. Since this is a major "show-stopper" ill release a new version later today addressing that issue among with some other bugs and optimizations. I don't see why not :)
  11. Thanks for the feedback jireland! That's a good suggestion. I will implement a limited draggable area in the top of the window for 1.3!
  12. The "Tab" buttons are generated automatically depending how many tabs you have in your profile XML. The "name" of the tab is specified in the XML aswell, Here is how the ShowcaseProfile.xml looks like (bolded the important parts and removed controls code) <?xml version="1.0" encoding="utf-8" ?> <Tabs> <MonitorID>2</MonitorID> <LatchTo>MiddleRight</LatchTo> <Tab> <ID>1</ID> [b]<Name>UFC Scale Test</Name>[/b] </Tab> <Tab> <ID>2</ID> [b]<Name>MFCD + UFC</Name>[/b] </Tab> <Tab> <ID>3</ID> [b]<Name>Test Panel</Name>[/b] </Tab> </Tabs> The "OFF" image is embedded in the executable and not modifiable :)
  13. Thanks! I'll be fixing that issue in the next release :) In HawgTouch dir\Images\TestPanel
  14. Full screen support is slated for future releases.
  15. Version 1.2 is out. Check out the main post for download link :)
  16. You are not a pain :) The way it works is kind of tricky so I try my best to explain how it is using my limited explaining abilities :P Rocker Switches have full transparency enabled. So your shadows should work. If they don't as of now be sure that in version 1.2 this issue is rectified. I can't wait for your UFC and an updated MFCD panel with no shadows :) I'm probably going to ship version 1.2 with an AHCP panel defined and a sample tabular profile :)
  17. Put my order today! :D
  18. I'll try my best to explain the transparency rules in HawgTouch. For the background image of any panel you create in HawgTouch, to create certain places transparent, you will need to color it in fuschia. The reason behind this is C# limitations. To make a certain "form" transparent you need to define a TransparencyKey property and give it an RGB value. Knowing that no one really uses Fuschia for anything I decided that it would be a good TransparencyKey value. With that, The panel background color is also Fuschia. This results in showing the image correctly. However, if there are "REAL" transparent pixels on the image, they would display as Fuschia because the form the picture is displayed on is colored Fuschia. The reason you see fuschia in your MFCD's is because these are "transparent" pixels which are non visible, showing the actual panel behind it which as explained earlier is fuschia colored. I took your MFCD frame and used photoshop to clear those real transparent pixels. Then I colored it fuschia in the background. If you try using the image I provided you will see that the MFCD main view area and the first OSB are drawn without any fuschia residue. While the rest gets it. Look at the image and try to see what I did there... I hope this explanation is good...This fuschia "trick" is only needed for the panel background images. All the actual clickable controls feature full regular transparency.
  19. Ill have to check why you get fuschia on your MFCD's. I'll look that up this weekend. Rocker switches support full transparency. I'll look into it. Panel sizes won't be a problem for the next version of HawgTouch. I have implemented a percentage based resizing mechanism for all panels. You can create a panel at any size you want, and in the profile definitions you can specify at which size percentage you want the panel to be rendered on screen. The following clip demonstrates the "scaling" options in the new version, Using only the graphics created by jeffyd123 for a single size UFC, you can see how the UFC can be resized freely. Also showing the new support for tabs. The tabs are still being worked on :) http://www.screencast.com/users/Aviad-Netcraft/folders/Jing/media/8c56e3f9-6a14-4c7d-be25-146007d92bbf Hope this helps :)
  20. Fuschia is the transparency key for the panels. To create a transparent slot you need to color it fuschia. Only panel background image uses the fuschia transparency key. For buttons you can put any image with regular transparency and it will draw correctly. This could be achieved but it would set me back quiet some time in development. Considering the types of controls and gauges I intend to implement in HawgTouch, I think that altering the current method would be quiet limited.
  21. Your UFC looks absolutely gorgeous! Can't wait for you to share it with us!
  22. A little update for the next version of HawgTouch: - Resizeable controls - You can now resize controls and panels to your liking without the need to produce complete new images for variant sizes. Of course down scaling will work better than up scaling. - Support for full screen panels - Allowing you to define specific panel as full screen. Upon loading the specified panel it will launch in full screen mode on the chosen monitor (for users with more than 2 monitors) - Tabs - Each profile will support tabs. All defined within the profile XML file, a tab switch control will pop up if the loaded profile has more than 1 tabs defined. - Audible clicks - Optional setting, allowing you to hear an audible "click" sound when a button has been pressed on HawgTouch. - Better key press engine which removes the "flashing" completely allowing a much smoother experience HawgTouch 1.2 will be released sometime around this upcoming weekend:) Oh and I'm still looking for a generous soul to maybe create a little logo and icon for this application due to my awful graphics skills :o
  23. Make sure you are running HawgTouch as administrator. HawgTouch is configured to run as a top most window which remains always on top. In addition to that I have implemented a timer inside the main loop which refreshes the windows position every few seconds. It seems to me this issue is related to ATI Eyefinity setup. Can anyone else running the said configuration try out and let us know whats the verdict? Also, if you can, PM me your monitor setups and resolutions. Ill try and replicate your conditions as far as I can and test it myself. I'm sure we can work it out :)
  24. In the current build, HT searches for the DCS window, set it as foreground and send keys to it. This is whats resulting the little "flashes". I've addressed that in the next build by setting HT as a non active window and sending the keystrokes to the currently focused window. This not only nullifies the "flashing" and sometimes keystrokes being missing but also enables HawgTouch to be used on any game that you are running. If you are running the simulator under Administrator privileges, you will have to launch HawgTouch as administrator as well. To do so, Right click HawgTouch shortcut or executable and select "Run as Administrator" (should have a little shield next to it). If you still can't get the keypresses sent try hitting multiple times and make sure that in your profile XML, the KeyCommand field is set to the appropriate key you mapped inside DCS A-10 control settings. If it still doesn't work PM me and I will do my best to help you troubleshoot this issue. I'm aware that long presses don't work currently. This issue have been addressed in the next version of HawgTouch. Tommy, your panels look incredible. First the wonderful MFCD and now the UFC! Thanks for putting effort into this :D
×
×
  • Create New...