Search Type: Posts; User: branflake2267

Page 1 of 5 1 2 3 4

Search: Search took 0.06 seconds.

  1. Thanks for the report! I have opened a bug in our bug tracker.
  2. This is our 2.3.1 docs

    Would that work?
  3. I've been able to replicate the issue. I'm not sure why yet, but I see it happening in our classic theme with SDM. I've file the issue EXTGWT-4400 for it.
  4. Sorry about that. We had noticed that just shortly after. Thanks for reporting!
  5. Thanks for the report! I have opened a bug in our bug tracker.
  6. I've got a versions matrix here to help out too.
  7. You're using GWT 2.6.1 and you'll have to upgrade to GWT 2.7 because of breaking changes in GWT.

    Does that help?
  8. We won't support Firefox 13. Why do you use such an old version?

    We know about some of the issues with triton working with old browsers that we do support.
  9. We don't have a 4.0.0-ea maven build yet available. But the nightly build of 4.0.0-SNAPSHOT is available to try out and has all the same commits as 4.0.0-ea.

    The artifacts are found here: ...
  10. We had a error in the zip. It has been corrected. Can you try download it again, it should have the Triton jar in the zip now.
  11. I'm investigating and will get back shortly,
  12. Thanks for the report! I have opened a bug in our bug tracker.
  13. Gotcha, I can understand the time constraint. Maybe there is another angle I can take to see if I can drill this with you. A test case is ideal but I understand the challenge.

    Could you provide a...
  14. I haven't seen this be an issue for anybody else except for that in GWT 2.6.1 when the resources were not copied on the init of SDM. I don't expect api to be at fault in this circumstance. I've done...
  15. This has been fixed in 3.1.4.
  16. This has been fixed and guards have been added.
  17. I'm not sure why you're having the issue then. I remember putting the clear.gif in the client/public folder and having it work as a workaround. If I could get a test project with the issue, I could...
  18. Sorry the patch didn't get integrated although is still up to bat. There is a workaround in the mean time. What I suggest doing is provide a text field with a custom appearance that removes the input...
  19. In GWT 2.7 the resources should be fixed, that means they get copied on booting dev mode. The first thing I recommend doing is double check to make sure no GWT 2.6.1 is on the classpath. I see this...
  20. Could you provide a test case that I could test locally? I wasn't able to replicate the issue. If I can replicate the issue, I we can fix it.
  21. This should work, I'm investigating.
  22. Thanks for reporting. I've added this to our issues.
  23. This smells like a bug. I'm checking and will get back to you soon.
  24. I'm doing some guessing here, but something like this could be done.

    Window w = new Window() {
    protected void onAfterFirstAttach() {
  25. You could work around this by sublcassing window and on the first attach, use the same logic that is used in draggable and/or maybe window.fitContainer.
Results 1 to 25 of 109
Page 1 of 5 1 2 3 4