Jump to content


uniGUI Subscriber
  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About aem

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yes, thank you. The two step process works fine for particular controls as in: 1. UniServerModule.CustomCSS: ._x-item-disabled .x-form-field { opacity: 1; -moz-opacity: 1; filter: alpha(opacity=100); color: dimgray; background: gainsboro; } 2. UniDBEdit->ClientEvents->UniEvents-> beforeInit fn: function beforeInit(sender, config) { config.disabledCls = "_x-item-disabled"; } But this would be unwieldly for dozens of forms and thousands of controls. What I was shooting for was maybe a simple one line that could be added to
  2. Although everyone loves the look that comes with the CLASSIC theme I get constant complaints about not being able to tell disabled items from enabled ones. It would be great if I could somehow use a slightly darker shade of gray for disabled items and do it globally (perhaps in customcss). What are the options here? thanks, tonyM
  3. Thank you for considering this silly question.... We changed all the synchronized grid places to use a scrollbox that contains multiple grids. Obvious once we thought of it. Keep up the great work. This has always been a great forum for quick responses about a fantastic product. sincerely, tonyM
  4. The idea is something like this. The user enters a set of special numbers (corresponding to a mix of claims and such) So a stack of simple grid cells seemed appropriate ( our VCL apps do this in several places). When the user is ready they click a button ANALYZE. Then to the right of each value a number of new values and messages are filled. They then 'work' with this list, going up and down the info, until done. Two grids connected using ONTOPLEFTCHANGED to reset the other grid's TOPROW property was a simple way to have the info scannable. - Of course
  5. Here is an example of two unistringgrids, side-by-side, that would be nice to scroll together. See what ya think, thanks, tonyMsyncedGrids.zip
  6. MORE: It looks like I could get rid of the several places where this two-grid-sync business is done if we could make specific columns readonly within a single tunistringgrid. We have explored that possibility before but come up dry. But that seems like an alternative if it were possible. thanks, tonyM
  7. We're porting another set of applications from VCL to UniGUI - and several of those forms have pairs of grids positioned right against each other. When either grid is scrolled the ONTOPLEFTCHANGED event sets the TOPROW property to match the other grid - slick. Is this synchronization doable without those? (I notice an event onalignposition that sounds interesting but nowhere do I see any references to it in docs or forums - It's probably irrelevant to my need anyway) thanks, tonyM
  8. Perfect. AjaxTimeout is the key. Thank you - UniGUI is an unbelievably clean product. tonyM
  9. Hello, While the tuniFileUpload component doesn't allow much customization - it does seem to get the job done. But when we began trying real files it fails for us consistently after about 30 seconds. The result is we can upload smallish files fine but anything over about 50mb gives a simple messagebox with: communication error We are using hyperserver only. We have tried both 0 and large values for maxAllowedsize We have tried this with the browser on the same machine as hyperserver to eliminate any true network issues. We have combe
  10. Hello, I am the developer using uniGUI and loving it. But the products being tested for release using Hyperserver on Cloud servers is being done by a small team elsewhere (very elsewhere). It looks as if anyone can 'sign up' on the main uniGUI Discussion Forums page by simply providing display name - email - new password. Will that allow my associate to read and create questions and topics? Would it make sense for me to create the account then pass the information on to the lead guy of that team? thanks, tonyM
  11. I have kept trying various things to try to make unimenutree items display and act as disabled when disabled at runtime (the user's rights are applied) disable the unimenuitem - no effect // welcome1.enabled:=false; //top level // personalchecks1.enabled:=false; //child level disable unitreemenu items directly - no effect //unitreemenu1.items[0].enabled:=false; //does nothing //unitreemenu1.items[4].enabled:=false; //does nothing The alternative is to hide the tree items - but property alone has no effect // welcome1.visible:=false;
  12. We use the tuniTreeMenu hooked to tuniMenuItems extensively - works great. I want to be able to disable all the items a user doesn't have the right to access at startup. But assigning values to 'enabled' has no effect. Possible? Anyway, I did find nice code in this group that lets me HIDE individual treemenu items. It works great for Top level items, but not for child items. Hmm. Even if I fully expand the tree items and then execute the code, sub-items don't seem to be affected. Here is an example test of mine: welcome1.enabled := False; //a top
  13. Mystery Solve. My apologies to the group. Our own source was the culprit it seems. Thank you, tonyM CC
  14. After several months of porting various programs to have web interfaces (for cloud deployment) we are ready to delve into the world of deployment. Our first step is to try out HyperServer - running our app compiled in simple stand-alone mode. Of course the simple steps are quite clear: Copy hyper_server.exe and hyper_server.cfg to folder where your application's executable file resides. •Compile your application in Standalone Server mode. You may need to change your project's DPR file to switch from a different mode to Standalone Server. •Edit hyper_server.cfg fil
  15. I have pursued the forum and tried several promising methods, but I cannot seem to be able to programmatically control the selected cell of the tunistringgrid. The tunistringgrid clearly maintains both a 'truly selected' cell and a highlighted cell. Ar runtime if you specify grid.row:=3; grid.col:=3; The cell 3,3 is indeed highlighted. But you can still discern a light line around the cell that had been selected earlier. And if the user hits the ENTER key, the editing occurs within that previous cell, not 3,3 as hope
  • Create New...