-
7 Mar 2012 6:50 AM #1
sencha designer 2.0 beta1 doesn't start
sencha designer 2.0 beta1 doesn't start
Hi I'm Gianluca Evangelisti,
I used sencha designer 2.0 beta1 for two days and it worked good.
This morning i had changed the port from 1530 to 8080 in configuration menù then i restarted the program but the user interface didn't appear more.
I tried to uninstall sencha designer and then i tried to reinstall sencha designer but nothing has changed.
What i can do for eliminate the problem?
Thanks and good evening
-
7 Mar 2012 6:56 AM #2
Hi Gianluca,
Can you attach a screen shot of where you changed the port? I cant recall a port anywhere except may during the install in proxy settings or URL prefix.
ThanksBharat Nagwani
Sencha Designer Development Team
-
7 Mar 2012 7:03 AM #3
sencha designer 2.0 beta1 doesn't start
sencha designer 2.0 beta1 doesn't start
I can't report the screenshoot because the user interface doesn't appear more but the port that i changed is in the url of menu config.
-
7 Mar 2012 11:41 AM #4
gianlucaevangelisti -
Could you zip up the following directory depending on your operating system and send it to us at designer.feedback@sencha.com?
Windows XP
C:\Documents and Settings\<username>\Local Settings\Application Data\Sencha, Inc\Sencha Designer 2.0\
Windows Vista/7
C:\Users\<username>\AppData\Local\Sencha, Inc\Sencha Designer 2.0\
Linux
~/.local/share/data/Sencha, Inc./Sencha Designer 2.0/
Mac OS X
~/Library/Application Support/Sencha, Inc./Sencha Designer 2.0/
After doing so, remove this directory and reinstall. Hopefully this should fix your install.Aaron Conran
@aconran
Sencha Architect Development Team
-
7 Mar 2012 2:53 PM #5
After you've zipped it up go ahead and remove the Sencha Designer 2.0/ directory and reinstall and see if that helps at all
Phil Strong
@philstrong
#SenchaArchitect
Sencha Architect Development Team
-
8 Mar 2012 12:09 AM #6
Now with yuor help sencha designer 2.0 works good.
Thanks
Success! Looks like we've fixed this one. According to our records the fix was applied for
a bug in our system
in
a recent build.


Reply With Quote